bnx2x_vlan_m...egistry_elem(9)
π bnx2x_vlan_mac_get_registry_elem β from the Kernel API Manual, section 9, bestie
okay so picture this: it's a kernel API manual page, section 9, and the star of the show is bnx2x_vlan_mac_get_registry_elem. she's giving main character energy and she's here to prepare a registry element. that's it. that's the whole vibe. π
β¨ NAME β¨
bnx2x_vlan_mac_get_registry_elem β literally just prepare a registry element. no cap, that's the entire job description. π
πΈ SYNOPSIS πΈ
int bnx2x_vlan_mac_get_registry_elem (struct bnx2x *bp , struct
bnx2x_vlan_mac_obj *o , struct bnx2x_exeq_elem *elem , bool restore ,
struct bnx2x_vlan_mac_registry_elem **re );
she takes five things and hands you back an int. iconic. π«Ά
π¦ ARGUMENTS π¦
bpβ the device handle. your whole device situation lives here, bestie π₯οΈoβ the vlan object. yes, her name is literally one letter. she's that girl.elemβ the element. the thing being element-y about.restoreβ "to restore or not" β it's abool, so it's giving restore or not restore, no in-between πreβ the registry. it's astruct bnx2x_vlan_mac_registry_elem **, so it's a pointer-to-pointer, so it's fancy like that β¨
π DESCRIPTION π
so what does she actually do? she prepares a registry element according to the current command request. that's the lore. that's the whole plot. she looks at whatever command is currently being requested and she preps a registry element to match it. lowkey elegant, highkey doing exactly one thing and doing it well. π
π₯ SEE ALSO π₯
you want the whole friend group? okay bestie, buckle up, because this is a long group chat and everybody's here. Kernel file: ./drivers/net/ethernet/broadcom/bnx2x/bnx2x_sp.c
bnx2x_exe_queue_init(9)bnx2x_exe_queue_add(9)bnx2x_exe_queue_step(9)bnx2x_state_wait(9)__bnx2x_vlan_mac_h_write_trylock(9)__bnx2x_vlan_mac_h_exec_pending(9)__bnx2x_vlan_mac_h_pend(9)__bnx2x_vlan_mac_h_write_unlock(9)__bnx2x_vlan_mac_h_read_lock(9)bnx2x_vlan_mac_h_read_lock(9)__bnx2x_vlan_mac_h_read_unlock(9)bnx2x_vlan_mac_h_read_unlock(9)bnx2x_vlan_mac_set_cmd_hdr_e2(9)bnx2x_vlan_mac_set_rdata_hdr_e2(9)bnx2x_vlan_mac_set_rdata_hdr_e1x(9)bnx2x_set_one_mac_e1x(9)bnx2x_set_one_vlan_mac_e1h(9)bnx2x_vlan_mac_restore(9)bnx2x_validate_vlan_mac_add(9)bnx2x_validate_vlan_mac_del(9)bnx2x_validate_vlan_mac_move(9)bnx2x_wait_vlan_mac(9)bnx2x_complete_vlan_mac(9)bnx2x_optimize_vlan_mac(9)bnx2x_execute_vlan_mac(9)bnx2x_config_vlan_mac(9)bnx2x_vlan_mac_del_all(9)bnx2x_mcast_get_next_bin(9)bnx2x_mcast_clear_first_bin(9)bnx2x_mcast_handle_restore_cmd_e2(9)bnx2x_mcast_handle_current_cmd(9)bnx2x_mcast_set_rdata_hdr_e2(9)bnx2x_mcast_refresh_registry_e2(9)bnx2x_mcast_set_rdata_hdr_e1(9)bnx2x_mcast_handle_restore_cmd_e1(9)bnx2x_get_fw_mac_addr(9)bnx2x_mcast_refresh_registry_e1(9)__atomic_add_ifless(9)__atomic_dec_ifmoe(9)bnx2x_init_credit_pool(9)bnx2x_debug_print_ind_table(9)bnx2x_setup_rss(9)bnx2x_queue_state_change(9)bnx2x_queue_comp_cmd(9)bnx2x_q_init(9)bnx2x_q_send_deactivate(9)bnx2x_q_send_activate(9)bnx2x_queue_chk_transition(9)bnx2x_func_state_change_comp(9)bnx2x_func_comp_cmd(9)bnx2x_func_chk_transition(9)bnx2x_func_init_func(9)bnx2x_func_init_port(9)bnx2x_func_init_cmn_chip(9)bnx2x_func_init_cmn(9)bnx2x_func_reset_func(9)bnx2x_func_reset_port(9)bnx2x_func_reset_cmn(9)bnx2x_func_state_change(9)
literally the whole extended family showed up to the function. iykyk. π
π real talk though: this page is auto-generated kernel API documentation, so if you're here looking for lore beyond "prepare a registry element according to the current command request", that's genuinely all she wrote. don't go reading extra behaviour into it, bestie. π
and that's the page! π§ source file is ./drivers/net/ethernet/broadco... (yes it's truncated in the footer, don't come for me) and the date on this bad boy is October 2026. mwah, bye bestie ππ·
π¦ 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