dev_change_carrier(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– dev_change_carrier(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this is the page for dev_change_carrier(9), and it is literally the shortest little guy in the whole dev_api family. no cap. let's get into it ✨


🌸 NAME 🌸

dev_change_carrier β€” change device carrier πŸ¦‹


✨ SYNOPSIS ✨

int dev_change_carrier (struct net_device *dev , bool new_carrier );

that's it. that's the whole signature. she's compact and she knows it πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device πŸ‘‘ (the one whose carrier you're about to mess with)
  • new_carrier β€” the new value ⭐ (like, the carrier value you want it to have now)

πŸ’œ DESCRIPTION πŸ’œ

Change device carrier. fr fr, that's the whole description β€” it changes the device carrier, periodt. lowkey iconic how little it needs to say πŸ™ˆ


πŸ”₯ RETURN πŸ”₯

  • 0 on success 🫢 slay
  • -errno on failure 😭 (you know the drill, the negative errno tells you what went wrong)

🌈 SEE ALSO 🌈

it's giving family reunion β€” the whole squad lives in the kernel file ./net/core/dev_api.c and honestly they're all must-follows:


πŸ’€ reminder bestie: this page does not promise anything beyond 0 on success and -errno on failure. don't go inventing extra return values, iykyk.

okay that's the whole page, you ate that πŸ“πŸ’… β€” this gem comes from ./net/core, dated October 2026, and it's filed under dev_change_carrier(9). mwah, go read the other dev_api pages now, ily πŸ§šπŸ’–

πŸ“¦ where this page comes from