qmi_recv_new_server(9)

✨ NAME ✨

okay so bestie, this page is qmi_recv_new_server(9) from the Kernel API Manual 💖 and the actual name is:

qmi_recv_new_server — handler of NEW_SERVER control message

---

🌸 SYNOPSIS 🌸

the whole vibe check is literally this one function call:

void qmi_recv_new_server (struct qmi_handle *qmi , unsigned int service , unsigned int instance , unsigned int node , unsigned int port );

---

🎀 ARGUMENTS 🎀

• qmi — qmi handle 🫶
• service — service id of the new server ✨
• instance — instance id of the new server 🦋
• node — node of the new server 🌸
• port — port of the new server 💅

---

💅 DESCRIPTION 💅

So what it does: it calls the new_server callback to inform the client about a newly registered server that matches the currently registered service lookup. that's the whole serve, no cap 🔥

---

🦋 SEE ALSO 🦋

the kernel file is ./drivers/soc/qcom/qmi_interface.c — and here's the full bestie list:

• qmi_recv_del_server(9)
• qmi_recv_bye(9)
• qmi_recv_del_client(9)
• qmi_add_lookup(9)
• qmi_add_server(9)
• qmi_txn_init(9)
• qmi_txn_wait(9)
• qmi_txn_cancel(9)
• qmi_invoke_handler(9)
• qmi_handle_net_reset(9)
• qmi_handle_init(9)
• qmi_handle_release(9)
• qmi_send_message(9)
• qmi_send_request(9)
• qmi_send_response(9)
• qmi_send_indication(9)

---

source/version: ./drivers/soc/qcom · date: October 2026 · page: qmi_recv_new_server(9) — mwah, bye bestie 💅🎀