summaryrefslogtreecommitdiff
path: root/lib/mpi/mpi-inline.c
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2025-04-09 17:55:41 +0300
committerJakub Kicinski <kuba@kernel.org>2025-04-15 00:05:56 +0300
commit747fb8413aaa36e4c988d45c4fe20d4c2b0778cd (patch)
treeb6fcb7a4cd6a387066e5933d03f52f05f56c35b0 /lib/mpi/mpi-inline.c
parentf0433eea468810aebd61d0b9d095e9acd6bea2ed (diff)
downloadlinux-747fb8413aaa36e4c988d45c4fe20d4c2b0778cd.tar.xz
netlink: specs: ovs_vport: align with C codegen capabilities
We started generating C code for OvS a while back, but actually C codegen only supports fixed headers specified at the family level right now (schema also allows specifying them per op). ovs_flow and ovs_datapath already specify the fixed header at the family level but ovs_vport does it per op. Move the property, all ops use the same header. This ensures YNL C sees the correct hdr_len: const struct ynl_family ynl_ovs_vport_family = { .name = "ovs_vport", - .hdr_len = sizeof(struct genlmsghdr), + .hdr_len = sizeof(struct genlmsghdr) + sizeof(struct ovs_header), }; Fixes: 7c59c9c8f202 ("tools: ynl: generate code for ovs families") Link: https://patch.msgid.link/20250409145541.580674-1-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'lib/mpi/mpi-inline.c')
0 files changed, 0 insertions, 0 deletions