ksz9477_flower_parse_key_l2(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ksz9477_flower_parse_key_l2(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes that's Kernel API Manual, capital letters, we're being official today πŸŽ€ and this page is literally all about ksz9477_flower_parse_key_l2. Sit down, hydrate, let's go.


✨ NAME ✨

ksz9477_flower_parse_key_l2 β€” it parses the Layer 2 key from a flow rule and then configures the ACL entries accordingly. that's it, that's the whole job, and honestly? she ate. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int ksz9477_flower_parse_key_l2 (struct ksz_device *dev , int port ,
struct netlink_ext_ack *extack , struct flow_rule *rule , unsigned long
cookie , u32 prio );

no cap, that's the whole signature β€” six args, one int coming back at you. 🫢


🌸 ARGUMENTS 🌸

every single one, bestie, we're not skipping anybody:

  • dev β€” a pointer to the struct ksz_device. the main character device struct, everything hangs off her πŸ‘‘
  • port β€” the port number. just a plain number, no drama. πŸ”’
  • extack β€” a pointer to the struct netlink_ext_ack. she's the messenger when things go sideways, iykyk.
  • rule β€” a pointer to the struct flow_rule. this is where the Layer 2 key is living and we're about to parse the heck out of it πŸ’–
  • cookie β€” the cookie you wanna associate with the entry πŸͺ (yes, literally called a cookie, we love that for us)
  • prio β€” the priority of the entry. a u32, iconic, no notes. ⭐

πŸ”₯ DESCRIPTION πŸ”₯

so here's the vibe check: this function parses the Layer 2 key out of the flow rule, then configures the corresponding ACL entries. that's the whole arc. πŸ¦‹

but before she goes ahead and starts configuring, she does her little pre-flight checks β€” she checks for unsupported offloads and for available entries before proceeding with the configuration. like a true responsible queen, she looks before she leaps. πŸ™ˆβœ¨

fr fr do not skip the vibe check β€” the whole point is she validates before she configures anything.

🌈 RETURN 🌈

  • 0 on success πŸ’–
  • a negative error code on failure 😭

that's it. zero means slay, negative means the situation has gone off the rails. πŸ’€


πŸŽ€ SEE ALSO πŸŽ€

go read these next, bestie, they're the friend group:

all of them, no cap, every single reference is right there. 🫢


and that's the page!! mwah πŸ’‹ huge sign-off energy: this little beauty lives in ./drivers/net/dsa/microchip, and she was stamped October 2026 β€” so yeah, she's dated, she's sourced, she's iconic, periodt. πŸŒˆπŸ‘‘πŸ“

πŸ“¦ where this page comes from