nfp_net_irq_lsc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfp_net_irq_lsc(9) β€” like, the whole manual page, bestie

Okay so real talk: this is the man page for nfp_net_irq_lsc, and it lives in the kernel API manual (yes, that (9) at the end is the section, iykyk). It's a tiny little page but we're gonna treat it with the respect it deserves πŸŽ€


✨ NAME ✨

nfp_net_irq_lsc β€” the interrupt service routine for link state changes πŸ’–

Like, that's it, that's the whole vibe: it's the ISR that fires when the link state does a little change. Main character energy for your NIC's link status 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

irqreturn_t nfp_net_irq_lsc (int irq , void *data );

That's the whole signature, no cap β€” it takes an int irq and a void *data, and hands you back an irqreturn_t. Clean, iconic, periodt ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • irq β€” the interrupt. Yeah, that's the whole description: Interrupt. She's a woman of few words πŸ’…
  • data β€” an opaque data structure. Opaque as in "don't peek, just pass it along," not opaque as in "rude" πŸ™ˆ

⭐ RETURN ⭐

It indicates if the interrupt has been handled. That's the assignment, that's the whole job 🫢

Ngl, the man page keeps this one short β€” so no extra lore from me, bestie. Just: it tells you whether the interrupt got handled, fr fr.

🌈 SEE ALSO 🌈

Here's the friend group πŸ‘‘ β€” and yes, I'm listing every single one, because we don't do "etc." in this house:

Lowkey a whole group chat in there 😭 but every single one is linked, slay πŸ’œ


And that's the page!! Sign-off time, because we gotta give credit where it's due πŸ’– this one comes from the source ./drivers/net/ethernet/netrono... (yep, that's how it's printed, truncated and all, we don't edit the original), dated October 2026 β€” and the page header was nfp_net_irq_lsc(9), manual name folded in right at the top like a little bow πŸŽ€ πŸ¦‹

πŸ“¦ where this page comes from