docs: networking: can: change bcm_msg_head frames member to support flexible array
authorAlex Tran <alex.t.tran@gmail.com>
Thu, 4 Sep 2025 03:17:09 +0000 (20:17 -0700)
committerMarc Kleine-Budde <mkl@pengutronix.de>
Tue, 9 Sep 2025 12:12:38 +0000 (14:12 +0200)
The documentation of the 'bcm_msg_head' struct does not match how
it is defined in 'bcm.h'. Changed the frames member to a flexible array,
matching the definition in the header file.

See commit 94dfc73e7cf4 ("treewide: uapi: Replace zero-length arrays with
flexible-array members")

Signed-off-by: Alex Tran <alex.t.tran@gmail.com>
Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
Link: https://patch.msgid.link/20250904031709.1426895-1-alex.t.tran@gmail.com
Fixes: 94dfc73e7cf4 ("treewide: uapi: Replace zero-length arrays with flexible-array members")
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217783
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Documentation/networking/can.rst

index bc1b585355f7ad99edf030f8816dc01aa3016035..7650c4b5be5f182c83b18916ea96fdd95183c553 100644 (file)
@@ -742,7 +742,7 @@ The broadcast manager sends responses to user space in the same form:
             struct timeval ival1, ival2;    /* count and subsequent interval */
             canid_t can_id;                 /* unique can_id for task */
             __u32 nframes;                  /* number of can_frames following */
-            struct can_frame frames[0];
+            struct can_frame frames[];
     };
 
 The aligned payload 'frames' uses the same basic CAN frame structure defined