memstick_next_req(9)

💅 memstick_next_req(9) — the kernel API manual, but make it make sense

okay so bestie, we're in the <pink>Kernel API Manual</pink> today and the star of the show is literally memstick_next_req — like, the whole page is named after it. it's a function the host driver calls to grab the next request it should be working on. no notes, it's iconic 🎀

---

✨ SYNOPSIS ✨

int memstick_next_req (struct memstick_host *host , struct
memstick_request **mrq );

that's the whole signature, copy it exactly, don't get cute with it 🫶

---

🌸 ARGUMENTS 🌸

• host — the host you're working with. the one and only. your main character host 👑
• mrq — a pointer where the request gets stuck in. yes literally, that's the deal — you hand it a pointer-to-pointer and it points it at the request 💅

---

💖 DESCRIPTION 💖

so here's the vibe: the host calls this function while it's in the idle state — and that means *mrq == NULL — or it calls it after it's finished the previous request, in which case *mrq should be pointing at that previous request ✨

and ngl, here's the important bit: if that previous request was unsuccessful, it gets retried for a predetermined number of times. like, the function is not just gonna let it slide, it's giving second chances (a set amount of them, no infinite loop energy here) 🔥

---

⭐ RETURN ⭐

a value of 0 means a new request was assigned to the host — we love a success story, slay 💖

otherwise you get a negative error code. so like, not zero = something went sideways, handle it bestie 😭

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/memstick/core/memstick.c
• memstick_detect_change(9)
• memstick_new_req(9)
• memstick_init_req_sg(9)
• memstick_init_req(9)
• memstick_set_rw_addr(9)
• memstick_alloc_host(9)
• memstick_add_host(9)
• memstick_remove_host(9)
• memstick_free_host(9)
• memstick_suspend_host(9)
• memstick_resume_host(9)

like the whole memstick friend group, fr fr — go read them all, iykyk 🐛

---

heads up bestie: the retry thing only kicks in when the previous request actually failed. don't go assuming retries happen out of nowhere — read the description again if you gotta 🌈

---

and that's the page! source lives in ./drivers/memstick/core, dated October 2026, and the whole thing is filed under memstick_next_req(9) — periodt, go forth and process those requests 💜🧚