ENUM QUEUE_ENTRY_FLAGS(9)

💅 enum queue_entry_flags(9) — bestie's guide to the queue entry flags

okay so this is a page from the Kernel API Manual, and we're talking about enum queue_entry_flags, which is literally just the ✨ status flags for a queue entry ✨. like, the little bookkeeping bits that tell you what's going on with one entry in the queue. no cap, that's the whole vibe.

🌸 SYNOPSIS

enum queue_entry_flags {
    ENTRY_BCN_ASSIGNED ,
    ENTRY_BCN_ENABLED ,
    ENTRY_OWNER_DEVICE_DATA ,
    ENTRY_DATA_PENDING ,
    ENTRY_DATA_IO_FAILED ,
    ENTRY_DATA_STATUS_PENDING

};

like, that's the whole enum bestie, six flags, copy it exactly, don't be weird about it 🫶

🎀 Constants

• ENTRY_BCN_ASSIGNED — this entry has been assigned to an interface. and like, as long as this bit is set, this entry may only be touched through the interface structure. so hands off unless you're going through the interface, iykyk 💅
• ENTRY_BCN_ENABLED — -- undescribed --. yeah. that's it. the docs literally do not describe it 😭 not me leaving it exactly as undescribed because I refuse to make stuff up, that's not the vibe.
• ENTRY_OWNER_DEVICE_DATA — this entry is owned by the device for data transfer (either TX or RX depending on the queue). so the entry should only be touched after the device has signaled it is done with it. do not touch early, that's a one-way ticket to chaos bestie 🔥
• ENTRY_DATA_PENDING — this entry contains a valid frame and is waiting for the signal to start sending. it's got the goods, it's just patiently waiting its turn ✨
• ENTRY_DATA_IO_FAILED — hardware indicated that an IO error occurred while transferring the data to the hardware. and because of that, no TX status report will be expected from the hardware. like, don't sit around waiting for one, it's not coming 💀
• ENTRY_DATA_STATUS_PENDING — the entry has been send to the device and returned. it is now waiting for the status reporting before the entry can be reused again. so like, it came back but it's still in its waiting era, don't reuse it yet 🧚

🦋 SEE ALSO

Kernel file ./drivers/net/wireless/ralink/rt2x00/rt2x00queue.h Entry frame size(9), enum data_queue_qid(9), enum skb_frame_desc_flags(9), struct skb_frame_desc(9), get_skb_frame_desc(9), enum rxdone_entry_desc_flags(9), RXDONE_SIGNAL_MASK(9), struct rxdone_entry_desc(9), enum txdone_entry_desc_flags(9), struct txdone_entry_desc(9), enum txentry_desc_flags(9), struct txentry_desc(9), struct queue_entry(9), enum queue_index(9), enum data_queue_flags(9), struct data_queue(9), queue_end(9), tx_queue_end(9), queue_next(9), queue_loop(9), queue_for_each(9), tx_queue_for_each(9), txall_queue_for_each(9), rt2x00queue_for_each_entry(9), rt2x00queue_empty(9), rt2x00queue_full(9), rt2x00queue_threshold(9), rt2x00queue_dma_timeout(9), _rt2x00_desc_read(9), rt2x00_desc_read(9), rt2x00_desc_write(9)

go read those too, bestie, they're all part of the same little friend group 💜

fr fr the headers up top say enum queue_entry_flags(9) on both sides — that's just the title hanging out, and the manual name is Kernel API Manual in case you were wondering 🌈

and that's the whole page!! mwah 💋

sign-off time: this little gem lives at ./drivers/net/wireless/ralink/... (yes, the path is literally truncated in the source, I'm not gonna invent the rest, that would be lying) and the date on it is October 2026 🌸 so like, mark your calendars, periodt. the manual name's enum queue_entry_flags(9) and it's iconic, we stan 👑🦋✨