From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Johannes Berg <johannes@sipsolutions.net>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Kalle Valo <kvalo@kernel.org>
Cc: <linux-wireless@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
<linux-hardening@vger.kernel.org>
Subject: Re: [RFC] wireless: ti: Can we just remove this flexible array?
Date: Wed, 20 Mar 2024 10:10:37 -0700 [thread overview]
Message-ID: <6ddf112f-29d7-42b6-8d80-b8ed8fd987ba@quicinc.com> (raw)
In-Reply-To: <e7204512f71e9232572fced208899f7b6baa920d.camel@sipsolutions.net>
On 3/20/2024 2:03 AM, Johannes Berg wrote:
> On Tue, 2024-03-19 at 18:42 -0600, Gustavo A. R. Silva wrote:
>>
>>>> - /* payload */
>>>> - u8 data[];
>>>> } __packed;
>>>
>
> Why not keep (or even add in the cases where it's not) the comment
> though?
For something called <foo>_header isn't it implicit that something will
probably follow?
prev parent reply other threads:[~2024-03-20 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 21:59 [RFC] wireless: ti: Can we just remove this flexible array? Gustavo A. R. Silva
2024-03-19 22:54 ` Jeff Johnson
2024-03-20 0:42 ` Gustavo A. R. Silva
2024-03-20 9:03 ` Johannes Berg
2024-03-20 17:10 ` Jeff Johnson [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=6ddf112f-29d7-42b6-8d80-b8ed8fd987ba@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=gustavo@embeddedor.com \
--cc=johannes@sipsolutions.net \
--cc=kvalo@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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