fman_port_get_device(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fman_port_get_device(9) β€” from the Kernel API Manual

okay so bestie, welcome to section 9 of the Kernel API Manual, and today's main character is fman_port_get_device β€” like, the whole page. no lengthy subtitle, no little tagline, the NAME section is literally just the name and nothing else. she's mysterious. she's giving minimalism. we respect it. πŸŽ€


✨ SYNOPSIS ✨

the whole spell, exactly as written, don't @ me:

struct device * fman_port_get_device (struct fman_port *port );

that's it. that's the vibe. one function, one argument, one struct device * coming back at you. πŸ’«


🌸 ARGUMENTS 🌸

  • port β€” a pointer to the FMan port device. that's the one and only thing you hand her. 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: this function gets you the struct device that's associated with the specified FMan port device. you come in holding your struct fman_port *, you walk out holding the struct device that belongs to it. that's the whole errand. match made in heaven, lowkey. πŸ’–


πŸ‘‘ RETURN πŸ‘‘

a pointer to the associated struct device. slay. ✨

ngl, that's exactly as much as the page says about it β€” a pointer to the associated struct device. no extra lore, no secret bonus returns, keep your expectations aligned with the docs, bestie. πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

go touch some related grass, iykyk:

all of them are section 9, all of them are family, go read them when you're done here. 🌈


and that's the whole page, bestie β€” no crumbs left behind πŸ“. this little love letter came out of ./drivers/net/ethernet/freesca... (yes, the footer really does truncate it like that, iconic) with an October 2026 date stamp, living its best life as fman_port_get_device(9) in the Kernel API Manual. periodt. πŸ’œπŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from