ENUM NL802154_SCAN_DONE_REASONS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

ok so this is the enum nl802154_scan_done_reasons page from the Kernel API Manual β€” yes bestie, the whole manual, we're doing this β€” and it's literally just about the End of scan reasons. that's the vibe. πŸ¦‹


✨ SYNOPSIS ✨

like, here's the whole enum, no cap:

enum nl802154_scan_done_reasons {
    __NL802154_SCAN_DONE_REASON_INVALID ,
    NL802154_SCAN_DONE_REASON_FINISHED ,
    NL802154_SCAN_DONE_REASON_ABORTED ,
    NL802154_SCAN_DONE_REASON_MAX

};

πŸŽ€ Constants πŸŽ€

ok these are the actual constants, and every single one of them matters so pay attention bestie πŸ’–

  • __NL802154_SCAN_DONE_REASON_INVALID β€” this one is scan done reason number 0, and number 0 is reserved. so like… not for you. hands off. πŸ™ˆ
  • NL802154_SCAN_DONE_REASON_FINISHED β€” the happy ending!! ✨ the scan just finished naturally after going through all the requested and possible (complex) channels. she did the work, she saw the channels, she slayed. πŸ‘‘
  • NL802154_SCAN_DONE_REASON_ABORTED β€” the scan was aborted upon user request. a Beacon Request command 😭 that's literally the whole description, we don't make the rules
  • NL802154_SCAN_DONE_REASON_MAX β€” the Maximum scan done reason attribute number. it's giving upper bound. it's giving final boss. πŸ”₯

🌈 SEE ALSO 🌈

go read the Kernel file ./include/net/nl802154.h for the enum β€” iykyk 🧚

and also these iconic little numbers, all (9) sections, per usual:

  • nl802154_wpan_phy_capability_attr(9)
  • enum nl802154_coord(9)
  • enum nl802154_scan_types(9)
  • enum nl802154_cca_modes(9)
  • enum nl802154_cca_opts(9)
  • enum nl802154_supported_bool_states(9)

ok that's the whole page, short and sweet fr fr πŸ“ this came out of ./include/net, dated October 2026, and it's the enum nl8021...done_reasons(9) page β€” mwah, periodt, go read the source bestie πŸ’œπŸŒΈ


πŸ“¦ where this page comes from