From: Paolo Abeni <pabeni@redhat.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Alex Tran <alex.t.tran@gmail.com>
Cc: mkl@pengutronix.de, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, 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 12:35:46 +0200 [thread overview]
Message-ID: <c649a695-caeb-4c20-b983-9035c396e145@redhat.com> (raw)
In-Reply-To: <a7c707b7-61e1-4c40-8708-f3331da96d34@hartkopp.net>
On 9/4/25 8:25 AM, Oliver Hartkopp wrote:
> On 04.09.25 05:17, 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>
>
> Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
@Mark, @Oliver: I assume you want us to apply this patch directly to the
net tree, am I correct?
If so, @Alex: please use a formal 'Fixes:' tag for the blamed commit and
'Link: to reference the bz entry, thanks!
Paolo
next prev parent reply other threads:[~2025-09-09 10:35 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 [this message]
2025-09-09 11:03 ` Marc Kleine-Budde
2025-09-09 11:59 ` Marc Kleine-Budde
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=c649a695-caeb-4c20-b983-9035c396e145@redhat.com \
--to=pabeni@redhat.com \
--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=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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