ES58X_SIZEOF_URB_CMD(9)

💖 NAME 💖

ES58X_SIZEOF_URB_CMD is giving “calculate the maximum length of an urb command for a given message field name.” This is the Kernel API Manual page, and the macro is lowkey the main character. 💅

✨ SYNOPSIS ✨

Here’s the exact summons, bestie — don’t mess with the spacing, the spacing is iconic:

ES58X_SIZEOF_URB_CMD (es58x_urb_cmd_type , msg_field );

🎀 ARGUMENTS 🎀

• es58x_urb_cmd_type — this is the type, and it has exactly two acceptable moods: either "struct es581_4_urb_cmd" or "struct es58x_fd_urb_cmd". Pick your fighter. 🦋
• msg_field — the name of the message field. That’s the whole assignment, no notes. ✨

🦋 DESCRIPTION 🦋

It must be a macro in order to accept the different command types as an input. Not me pointing out that the macro-ness is load-bearing — it’s literally required, periodt. 💀

🌸 RETURN 🌸

The return value is the length of the urb command. Short, sweet, and it ate. 🔥

💜 SEE ALSO 💜

Kernel file: ./drivers/net/can/usb/etas_es58x/es58x_core.h

The rest of the friend group is right here — enums, structs, functions, the whole iconic lineup, iykyk:

• enum es58x_driver_info(9)
• enum es58x_physical_layer(9)
• enum es58x_sync_edge(9)
• enum es58x_flag(9)
• enum es58x_err(9)
• enum es58x_event(9)
• struct es58x_priv(9)
• struct es58x_parameters(9)
• struct es58x_operators(9)
• struct es58x_sw_version(9)
• struct es58x_hw_revision(9)
• struct es58x_device(9)
• es58x_sizeof_es58x_device(9)
• es58x_check_msg_len(9)
• es58x_check_msg_max_len(9)
• es58x_msg_num_element(9)
• es58x_priv(9)
• es58x_get_urb_cmd_len(9)
• es58x_get_netdev(9)
• es58x_get_raw_can_id(9)
• es58x_get_flags(9)

Okay that’s the whole scroll, bestie. Source is ./drivers/net/can/usb/etas_es58x, date is October 2026, and this is ES58X_SIZEOF_URB_CMD(9) from the Kernel API Manual. Love you, bye, hydrate. 💖🧚