From: "Gustavo A. R. Silva" <gustavoars@kernel•org>
To: Leon Romanovsky <leon@kernel•org>
Cc: Kees Cook <keescook@chromium•org>,
GR-QLogic-Storage-Upstream@marvell•com,
linux-alpha@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-ia64@vger•kernel.org, linux-s390@vger•kernel.org,
linux-sh@vger•kernel.org, sparclinux@vger•kernel.org,
linux-um@lists•infradead.org, linux-xtensa@linux-xtensa•org,
linux-crypto@vger•kernel.org, intel-gfx@lists•freedesktop.org,
dri-devel@lists•freedesktop.org, nouveau@lists•freedesktop.org,
coresight@lists•linaro.org, linux-arm-kernel@lists•infradead.org,
bcm-kernel-feedback-list@broadcom•com, netdev@vger•kernel.org,
linux-omap@vger•kernel.org, linux-scsi@vger•kernel.org,
target-devel@vger•kernel.org, mpi3mr-linuxdrv.pdl@broadcom•com,
linux-staging@lists•linux.dev,
linux-rpi-kernel@lists•infradead.org, sparmaintainer@unisys•com,
linux-cifs@vger•kernel.org, samba-technical@lists•samba.org,
linux-ext4@vger•kernel.org, linux-acpi@vger•kernel.org,
devel@acpica•org, linux-arch@vger•kernel.org, linux-mm@kvack•org,
greybus-dev@lists•linaro.org, linux-i3c@lists•infradead.org,
linux-rdma@vger•kernel.org, linux-bluetooth@vger•kernel.org,
alsa-devel@alsa-project•org, devicetree@vger•kernel.org,
linux-perf-users@vger•kernel.org,
linux-hardening@vger•kernel.org
Subject: Re: [PATCH][next] treewide: Replace zero-length arrays with flexible-array members
Date: Tue, 15 Feb 2022 13:32:21 -0600 [thread overview]
Message-ID: <20220215193221.GA884407@embeddedor> (raw)
In-Reply-To: <Ygv8wY75hNqS7zO6@unreal>
On Tue, Feb 15, 2022 at 09:19:29PM +0200, Leon Romanovsky wrote:
> On Tue, Feb 15, 2022 at 01:21:10PM -0600, Gustavo A. R. Silva wrote:
> > On Tue, Feb 15, 2022 at 10:17:40AM -0800, Kees Cook wrote:
> > > On Tue, Feb 15, 2022 at 11:47:43AM -0600, Gustavo A. R. Silva wrote:
> > >
> > > These all look trivially correct to me. Only two didn't have the end of
> > > the struct visible in the patch, and checking those showed them to be
> > > trailing members as well, so:
> > >
> > > Reviewed-by: Kees Cook <keescook@chromium•org>
> >
> > I'll add this to my -next tree.
>
> I would like to ask you to send mlx5 patch separately to netdev. We are working
> to delete that file completely and prefer to avoid from unnecessary merge conflicts.
Oh OK. Sure thing; I will do so.
Thanks
--
Gustavo
next prev parent reply other threads:[~2022-02-15 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 17:47 [PATCH][next] treewide: Replace zero-length arrays with flexible-array members Gustavo A. R. Silva
2022-02-15 18:17 ` Kees Cook
2022-02-15 19:21 ` Gustavo A. R. Silva
2022-02-15 19:19 ` Leon Romanovsky
2022-02-15 19:32 ` Gustavo A. R. Silva [this message]
2022-02-16 19:05 ` Rafael J. Wysocki
2022-02-16 19:46 ` Gustavo A. R. Silva
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=20220215193221.GA884407@embeddedor \
--to=gustavoars@kernel$(echo .)org \
--cc=GR-QLogic-Storage-Upstream@marvell$(echo .)com \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=coresight@lists$(echo .)linaro.org \
--cc=devel@acpica$(echo .)org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=greybus-dev@lists$(echo .)linaro.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=keescook@chromium$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-bluetooth@vger$(echo .)kernel.org \
--cc=linux-cifs@vger$(echo .)kernel.org \
--cc=linux-crypto@vger$(echo .)kernel.org \
--cc=linux-ext4@vger$(echo .)kernel.org \
--cc=linux-hardening@vger$(echo .)kernel.org \
--cc=linux-i3c@lists$(echo .)infradead.org \
--cc=linux-ia64@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-omap@vger$(echo .)kernel.org \
--cc=linux-perf-users@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=linux-rpi-kernel@lists$(echo .)infradead.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=linux-sh@vger$(echo .)kernel.org \
--cc=linux-staging@lists$(echo .)linux.dev \
--cc=linux-um@lists$(echo .)infradead.org \
--cc=linux-xtensa@linux-xtensa$(echo .)org \
--cc=mpi3mr-linuxdrv.pdl@broadcom$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nouveau@lists$(echo .)freedesktop.org \
--cc=samba-technical@lists$(echo .)samba.org \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=sparmaintainer@unisys$(echo .)com \
--cc=target-devel@vger$(echo .)kernel.org \
/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