ENUM IWL_MLD_REORDER_RESULT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

enum iwl_mld_reorder_result β€” the possible return values for iwl_mld_reorder(), and bestie, what they do is tell the caller how to handle the skb based on the result. That's the whole vibe: the enum is basically a little note back to whoever called, saying "here's what to do with this skb now." πŸ’Œ


✨ SYNOPSIS ✨

So the shape of it, literally:

enum iwl_mld_reorder_result {
    IWL_MLD_PASS_SKB ,
    IWL_MLD_BUFFERED_SKB ,
    IWL_MLD_DROP_SKB

};

Three constants, three moods, no cap. πŸ’…


πŸŽ€ Constants πŸŽ€

Okay so let's get into each one, because they each have main character energy in their own way:

  • IWL_MLD_PASS_SKB β€” the skb should be passed to the upper layer. It's giving "you're free, go be great" πŸ¦‹
  • IWL_MLD_BUFFERED_SKB β€” the skb has been buffered, so like… don't pass it to the upper layer. It's already chilling somewhere. πŸ›‹οΈ
  • IWL_MLD_DROP_SKB β€” the skb should be dropped and freed by the caller. Yeah, it's a whole goodbye situation, but the caller is the one who has to drop it and free it β€” not us. πŸ‘‹

πŸ’– SEE ALSO πŸ’–

Peep the kernel file ./drivers/net/wireless/intel/iwlwifi/mld/agg.h for the full lore, plus these iconic neighbours:

  • struct iwl_mld_reorder_buffer(9)
  • struct iwl_mld_reorder_buf_entry(9)
  • struct iwl_mld_baid_data(9)
  • struct iwl_mld_delba_data(9)

And that's the page, bestie β€” brought to you by the source over at ./drivers/net/wireless/intel/i..., dated October 2026, filed ever so lovingly under enum iwl_mld_reorder_result(9). Go pass those skbs responsibly πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from