ENUM W1_CN_MSG_FLAGS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum w1_cn_msg_flags(9) πŸ’…

okay so this is the Kernel API Manual page for enum w1_cn_msg_flags(9), and it's giving tiny-but-mighty enum energy. The whole vibe? Bitfield flags for struct cn_msg.flags. No cap, that's the assignment.

🌸 NAME 🌸

enum w1_cn_msg_flags β€” bitfield flags for struct cn_msg.flags. One enum, one flag, main character energy. Slay.

✨ SYNOPSIS ✨

The enum literally looks like this, and we are keeping it exactly:

enum w1_cn_msg_flags {
    W1_CN_BUNDLE

};

πŸŽ€ Constants πŸŽ€

  • W1_CN_BUNDLE β€” Request bundling replies into fewer messagse (yes, that's the original spelling, and it's part of the lore now 😭). Be prepared to handle multiple struct cn_msg, struct w1_netlink_msg, and struct w1_netlink_cmd in one packet. So your code needs to be ready for a whole little packet party, not just one lonely struct.

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/w1/w1_netlink.h β€” plus the whole friend group in order: enum w1_netlink_message_types(9), struct w1_netlink_msg(9), enum w1_commands(9), struct w1_netlink_cmd(9). Go read them, bestie, it's giving connected lore.


πŸ’– source/version: ./drivers/w1 Β· date: October 2026 Β· page: enum w1_cn_msg_flags(9) β€” that's the sign-off, and it ate. πŸŽ€βœ¨

πŸ“¦ where this page comes from