qmi_send_response(9)

📦 version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the Kernel API Manual entry for qmi_send_response(9) — yes, that's the title and the manual name folded in near the top like a cute little intro instead of a boring duplicated header 💅✨

✨ NAME ✨

qmi_send_response — send a response QMI message. that's the whole vibe: you're sending a response QMI message, bestie 💌

🎀 SYNOPSIS 🎀

ssize_t qmi_send_response (struct qmi_handle *qmi , struct sockaddr_qrtr *sq , struct qmi_txn *txn , int msg_id , size_t len , const struct qmi_elem_info *ei , const void *c_struct );

💅 ARGUMENTS 💅

  • qmi — QMI client handle; it's your QMI client handle, the main-character handle for this whole operation 👑
  • sq — destination sockaddr; the destination sockaddr for the message, like the address label bestie 🏷️
  • txn — transaction object to use for the message; the transaction object this message should use, no cap 🧾
  • msg_id — message id; the message id, obviously, keep it exact 🔢
  • len — max length of the QMI message; the max length of the QMI message, so yes, a max length, not a suggestion 🙈
  • ei — QMI message description; the QMI message description, aka the QMI message's whole description situation 🧚
  • c_struct — object to be encoded; the object that's gonna be encoded, put it in the codec bestie 💅

🫶 RETURN 🫶

0 on success, negative errno on failure. so: slay = 0, nope = negative errno, periodt 😭

🌈 SEE ALSO 🌈

Kernel file: ./drivers/soc/qcom/qmi_interface.c — yes, that exact path, iykyk 👀

the whole squad, all (9) refs:

xoxo, sourced from ./drivers/soc/qcom, dated October 2026, and this was qmi_send_response(9) — bye bestie 🫶💖🌈

📦 where this page comes from