ENUM W1_CN_MSG_FLAGS(9)
π 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 multiplestruct cn_msg,struct w1_netlink_msg, andstruct w1_netlink_cmdin 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms