can_proto_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ can_proto_register(9) ✨

okay so bestie, welcome to the Kernel API Manual β€” yes, the Kernel API Manual, we're doing kernel stuff today and honestly? kind of iconic of us. this little page is all about can_proto_register, and it's gonna be so chill, i promise 🫢


🌸 NAME 🌸

can_proto_register β€” register a CAN transport protocol πŸ’…

like, you're putting your protocol on the map. main character registration energy.


πŸ¦‹ SYNOPSIS πŸ¦‹

int can_proto_register (const struct can_proto *cp );

πŸŽ€ ARGUMENTS πŸŽ€

  • cp β€” pointer to the CAN protocol structure. that's it, that's the whole argument. she's a pointer, she points at a struct can_proto, slay πŸ’–

⭐ RETURN ⭐

so here's the vibe check on what you get back:

  • 0 β€” on success ✨ we love a clean zero, no notes
  • -EINVAL β€” the protocol number is invalid (out of range, bestie, it's out of range 😭)
  • -EBUSY β€” protocol already in use, someone else got there first, tragic
  • -ENOBUF β€” if proto_register fails
ngl, that last one is literally just "if proto_register fails" β€” that's the whole note. no cap.

🌈 SEE ALSO 🌈

so you wanna keep exploring? here's the whole squad πŸ‘‘

like, can_proto_unregister(9) is literally right there when you're done being registered. balance. 🧚


and that's the page, bestie! brought to you by the legends over at ./net/can, dated October 2026, and yes the header/footer energy is can_proto_register(9) all the way through. go register something cute πŸ’œπŸ”₯

πŸ“¦ where this page comes from