From: Kalle Valo <kvalo@codeaurora•org>
To: "Gustavo A. R. Silva" <gustavoars@kernel•org>
Cc: Len Baker <len.baker@gmx•com>,
Arend van Spriel <aspriel@gmail•com>,
Franky Lin <franky.lin@broadcom•com>,
Hante Meuleman <hante.meuleman@broadcom•com>,
Chi-hsien Lin <chi-hsien.lin@infineon•com>,
Wright Feng <wright.feng@infineon•com>,
Chung-hsien Hsu <chung-hsien.hsu@infineon•com>,
"David S. Miller" <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
"Gustavo A. R. Silva" <gustavo@embeddedor•com>,
Kees Cook <keescook@chromium•org>,
Shawn Guo <shawn.guo@linaro•org>,
linux-wireless@vger•kernel.org,
brcm80211-dev-list.pdl@broadcom•com,
SHA-cyfmac-dev-list@infineon•com, netdev@vger•kernel.org,
linux-hardening@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: [PATCH] brcmfmac: Replace zero-length array with flexible array member
Date: Tue, 21 Sep 2021 08:55:59 +0300 [thread overview]
Message-ID: <871r5iwjyo.fsf@codeaurora.org> (raw)
In-Reply-To: <87o88sy2gk.fsf@codeaurora.org> (Kalle Valo's message of "Thu, 16 Sep 2021 18:17:31 +0300")
Kalle Valo <kvalo@codeaurora•org> writes:
> "Gustavo A. R. Silva" <gustavoars@kernel•org> writes:
>
>> On Sat, Sep 04, 2021 at 11:22:17AM +0200, Len Baker wrote:
>>> There is a regular need in the kernel to provide a way to declare
>>> having a dynamically sized set of trailing elements in a structure.
>>> Kernel code should always use "flexible array members"[1] for these
>>> cases. The older style of one-element or zero-length arrays should
>>> no longer be used[2].
>>>
>>> Also, make use of the struct_size() helper in devm_kzalloc().
>>>
>>> [1] https://en.wikipedia.org/wiki/Flexible_array_member
>>> [2]
>>> https://www.kernel.org/doc/html/v5.14/process/deprecated.html#zero-length-and-one-element-arrays
>>>
>>> Signed-off-by: Len Baker <len.baker@gmx•com>
>>
>> Reviewed-by: Gustavo A. R. Silva <gustavoars@kernel•org>
>>
>> I'll take this in my -next tree. :)
>
> Why? It should go to wireless-drivers-next.
Gustavo, so have you dropped this from your tree now? I do not want to
get any conflicts because of this.
I'll reiterate again: do not take any patches touching
drivers/net/wireless unless I have acked them.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2021-09-21 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-04 9:22 [PATCH] brcmfmac: Replace zero-length array with flexible array member Len Baker
2021-09-12 19:15 ` Gustavo A. R. Silva
2021-09-16 15:17 ` Kalle Valo
2021-09-21 5:55 ` Kalle Valo [this message]
2021-09-21 17:37 ` Gustavo A. R. Silva
2021-09-24 11:20 ` Kalle Valo
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=871r5iwjyo.fsf@codeaurora.org \
--to=kvalo@codeaurora$(echo .)org \
--cc=SHA-cyfmac-dev-list@infineon$(echo .)com \
--cc=aspriel@gmail$(echo .)com \
--cc=brcm80211-dev-list.pdl@broadcom$(echo .)com \
--cc=chi-hsien.lin@infineon$(echo .)com \
--cc=chung-hsien.hsu@infineon$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=franky.lin@broadcom$(echo .)com \
--cc=gustavo@embeddedor$(echo .)com \
--cc=gustavoars@kernel$(echo .)org \
--cc=hante.meuleman@broadcom$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=len.baker@gmx$(echo .)com \
--cc=linux-hardening@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shawn.guo@linaro$(echo .)org \
--cc=wright.feng@infineon$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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