ksz9477_acl...le_add_match(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ksz9477_acl_processing_rule_add_match — from the Kernel API Manual, bestie ✨

okay so we're diving into the Kernel API Manual today and honestly? this one's a lil gem 🎀

🌸 NAME 🌸

ksz9477_acl_processing_rule_add_match — literally just adds a matching rule to the rule set, that's the whole vibe 💖

✨ SYNOPSIS ✨

void ksz9477_acl_processing_rule_add_match (u8 *entry , u8 match_idx );

like, it returns void, it takes two args, no drama, no cap 🫶

🦋 ARGUMENTS 🦋

  • entry — Pointer to the ACL entry 👑 that's the thing we're messing with
  • match_idx — Index of the matching rule to be added 🎯 which one are we picking, bestie

💜 DESCRIPTION 💜

So what does this icon actually do? It adds a matching rule to the rule set by updating the appropriate bits in the entry's rule set registers ✨ That's it. That's the whole job. Lowkey elegant, highkey iconic.

Now let's talk Access Control List (ACL) Processing Rule Registers because this is the part where the lore gets real 📖

  • 0x0E - RuleSet [15:8] — Bits 7:0 - RuleSet [15:8] 🌈 This one specifies a set of one or more Matching rule entries. RuleSet has one bit for each of the 16 Matching rule entries. And listen 👀 if multiple Matching rules are selected, then all conditions will be AND'ed to produce a final match result — fr fr, they all gotta agree:
    • 0 = Matching rule not selected 🙈
    • 1 = Matching rule selected 💅
  • 0x0F - RuleSet [7:0] — Bits 7:0 - RuleSet [7:0] ⭐ that's it, that's the entry, she's simple, we respect her
bestie reminder: the 0x0F register's description is literally just "Bits 7:0 - RuleSet [7:0]" in the source — don't go reading extra meaning into it, iykyk 🧚

🔥 SEE ALSO 🔥

k bye bestie!! 🦋 this page came straight outta ./drivers/net/dsa/microchip and it's dated October 2026 — slay, she's from the future 💀👑 hope this made ACL registers make sense, mwah 🍓💜

📦 where this page comes from