STRUCT MHI_RESULT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct mhi_result(9) β€” Completed buffer information

okay so bestie, this is a page out of the Kernel API Manual (yes, that one), and it's literally just one little struct that tells you what happened to a buffer after it finished doing its thing. She's short, she's iconic, she's giving "receipts after the transaction." Let's get into it 🫢


✨ NAME ✨

struct mhi_result β€” completed buffer information πŸ“¦

Like, the whole personality is: "here's what the buffer looked like when it was done." No cap.


🌸 SYNOPSIS 🌸

struct mhi_result {
    void *buf_addr;
    size_t bytes_xferd;
    enum dma_data_direction dir;
    int transaction_status;
 };

Look at her. Four fields. Immaculate. πŸ’…


πŸŽ€ Members πŸŽ€

  • buf_addr β€” the address of the data buffer. literally where the data lives, bestie πŸ“
  • bytes_xferd β€” the # of bytes transferred. yeah it's spelled like that, don't come for her πŸ™ˆ
  • dir β€” the channel direction. which way the vibe is flowing πŸ¦‹
  • transaction_status β€” the status of the last transaction. did it slay or did it flop, this field knows πŸ”₯

🌈 SEE ALSO 🌈

So there's a whole friend group, and honestly? The group chat is popping off. Start with the kernel file ./include/linux/mhi.h, then meet the rest of the squad:

Forty-nine whole entries and not a single one skipped, because we do NOT leave members of the squad out of the tag πŸ’œ

ngl if you're reading this at 3am trying to debug a transfer, hydrate, blink, and go read ./include/linux/mhi.h. the source is right there and it's free πŸ“

✨ that's the whole page, bestie β€” short, sweet, and fully documented ✨

Cute little sign-off: this page lives out of ./include/linux and it's dated October 2026 (time-traveling kernel docs, we love to see it 🧚), filed under struct mhi_result(9). byeeee πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from