ksz9477_get_..._block_start(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ksz9477_get_next_block_start β€” NAME ✨

ok so this is ksz9477_get_next_block_start, and it lives in the Kernel API Manual (yep, the (9) girlies, section 9, we love her). her whole job? identify the starting index of the next ACL block. that's it. that's the vibe. πŸŽ€


🌸 SYNOPSIS 🌸

int ksz9477_get_next_block_start (struct ksz_device *dev , int port ,
       int start );

like, three args, one int back. lowkey elegant ngl πŸ¦‹


✨ ARGUMENTS ✨

  • dev β€” pointer to the device structure. the main character of the whole struct situation πŸ’–
  • port β€” the port number where the ACL entries are being checked. yes, that port. 🫢
  • start β€” the starting index the search kicks off from. where we begin, bestie. ⭐

πŸ’« DESCRIPTION πŸ’«

okay so picture this: the function goes looking for the next valid ACL block, starting from the provided invalid one β€” or, if it hits the end of the ACL entries without finding another block, it returns the maximum ACL entries count. that's the whole quest. no cap. πŸ”₯

(it's giving "search party but for ACL blocks" and honestly? obsessed. πŸ’…)


πŸ‘‘ RETURN πŸ‘‘

  • the starting index of the next valid ACL block πŸŽ€
  • KSZ9477_ACL_MAX_ENTRIES if no other valid blocks are found after start πŸ™ˆ
  • a negative error code if an error occurs while checking 😭

🌈 SEE ALSO 🌈

kernel file: ./drivers/net/dsa/microchip/ksz9477_acl.c β€” go read her, she's iconic πŸ“–


and that's the whole page bestie, ily, go forth and find your next block πŸ’œ

sign-off szn: this one's from ./drivers/net/dsa/microchip, dated October 2026 β€” and it's literally ksz9477_get_..._block_start(9) all over again 🫢✨

πŸ“¦ where this page comes from