octep_ctrl_n..._link_status(9)
π octep_ctrl_net_set_link_status β kernel API manual, bestie edition π
okay so real quick before we dive in: this is a page from the Kernel API Manual (yes, the manual manual, section 9, the fancy kernel one) and we're talking about octep_ctrl_net_set_link_status. It's giving "I talk to firmware so you don't have to" energy and honestly? iconic. π¦
β¨ NAME β¨
octep_ctrl_net_set_link_status β set the link status in the firmware. that's it. that's the whole job. π
β¨ SYNOPSIS β¨
int octep_ctrl_net_set_link_status (struct octep_device *oct , int vfid
, bool up , bool wait_for_response );
it returns an int, it takes four things, and it's coming for your link status. periodt. π₯
β¨ ARGUMENTS β¨
octβ a non-null pointer to astruct octep_device. non-null, bestie. do NOT come in here with aNULLand expect a good time πvfidβ the index of the virtual function. it's anint. it's a whole number. it's the vf identity. slay π«Άupβ aboolstatus. boolean. yes/no. up or not-up. the vibe check in binary πwait_for_responseβ poll for a response. literally just "do we hang around waiting to hear back." ngl this one's doing main character energy in the argument list πΈ
β¨ DESCRIPTION β¨
so the function does its thing and here's the return situation, no cap:
return value: 0 on success, -errno on failure
that's the whole deal. 0 means we ate and left no crumbs β¨. -errno means something went sideways and the error code is coming to tell you about it. π
β¨ SEE ALSO β¨
okay this list is LONG and honestly it's giving "family reunion" but every single one of these is invited so let's go π
- the kernel file
./drivers/net/ethernet/marvell/octeon_ep/octep_ctrl_net.hβ yes that's the actual path, go look at it, iykyk π octep_ctrl_net_init(9)octep_ctrl_net_get_link_status(9)octep_ctrl_net_set_rx_state(9)octep_ctrl_net_get_mac_addr(9)octep_ctrl_net_set_mac_addr(9)octep_ctrl_net_get_mtu(9)octep_ctrl_net_set_mtu(9)octep_ctrl_net_get_if_stats(9)octep_ctrl_net_get_link_info(9)octep_ctrl_net_set_link_info(9)octep_ctrl_net_recv_fw_messages(9)octep_ctrl_net_get_info(9)octep_ctrl_net_dev_remove(9)octep_ctrl_net_set_offloads(9)octep_ctrl_net_uninit(9)
every single one accounted for. nobody left on read. π
β friendly reminder thatoctreally does need to be a non-null pointer to astruct octep_deviceand the manual says it plainly β that's the one non-negotiable in this whole page. π§
and that's the page, bestie!! π source path was ./drivers/net/ethernet/marvell..., dated October 2026, and the page title is octep_ctrl_n..._link_status(9) in case you were wondering β mwah, go set some link status, ily πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms