From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Alex Tran <alex.t.tran@gmail.com>
Cc: socketcan@hartkopp.net, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] docs: networking: can: change bcm_msg_head frames member to support flexible array
Date: Tue, 9 Sep 2025 13:59:50 +0200 [thread overview]
Message-ID: <20250909-fancy-practical-labrador-360abc-mkl@pengutronix.de> (raw)
In-Reply-To: <20250904031709.1426895-1-alex.t.tran@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
On 03.09.2025 20:17:09, Alex Tran wrote:
> 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")
>
> Bug 217783 <https://bugzilla.kernel.org/show_bug.cgi?id=217783>
>
> Signed-off-by: Alex Tran <alex.t.tran@gmail.com>
Applied to linux-can.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-09-09 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 3:17 [PATCH v1] docs: networking: can: change bcm_msg_head frames member to support flexible array Alex Tran
2025-09-04 6:25 ` Oliver Hartkopp
2025-09-09 10:35 ` Paolo Abeni
2025-09-09 11:03 ` Marc Kleine-Budde
2025-09-09 11:59 ` Marc Kleine-Budde [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250909-fancy-practical-labrador-360abc-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=alex.t.tran@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=socketcan@hartkopp.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox