ksz9477_flower_parse_key(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, this is the ksz9477_flower_parse_key(9) page from the Kernel API Manual, and the whole point is literally to parse flow rule keys for a specified port on a ksz_device. no cap, that's the function's main character job. πŸ’…


✨ SYNOPSIS ✨

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

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the ksz_device instance. it's giving "the device we're working with," obviously.
  • port β€” the port number to parse the flow rule keys for.
  • extack β€” the netlink extended ACK for reporting errors.
  • rule β€” the flow_rule to parse.
  • cookie β€” the cookie to associate with the entry.
  • prio β€” the priority of the entry.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the vibe check: this function checks if the used keys in the flow rule are supported by the device, and it parses the L2 keys if they match. slay.

🚨 if unsupported keys are used, an error message is set in the extended ACK. so yeah, it does not just ignore the problem β€” it reports it. periodt.

πŸ’– RETURN πŸ’–

0 on success, or a negative error code on failure. simple as that, bestie. 🫢


🌈 SEE ALSO 🌈

the receipts live in the kernel file:

  • ./drivers/net/dsa/microchip/ksz9477_tc_flower.c

and these other pages are linked too:


this page's source/version is ./drivers/net/dsa/microchip, dated October 2026, and the manual name is ksz9477_flower_parse_key(9) β€” periodt. πŸ’…βœ¨

πŸ“¦ where this page comes from