From: Saeed Mahameed <saeedm@mellanox.com>
To: "kuba@kernel.org" <kuba@kernel.org>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Leon Romanovsky <leonro@mellanox.com>,
"gustavoars@kernel.org" <gustavoars@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/mlx5: Replace zero-length array with flexible-array
Date: Sat, 9 May 2020 23:43:08 +0000 [thread overview]
Message-ID: <fb46eb601f979d5d8d95ec5749ae06c1bc86d469.camel@mellanox.com> (raw)
In-Reply-To: <20200508163642.273bda4f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Fri, 2020-05-08 at 16:36 -0700, Jakub Kicinski wrote:
> On Thu, 7 May 2020 13:59:35 -0500 Gustavo A. R. Silva wrote:
> > The current codebase makes use of the zero-length array language
> > extension to the C90 standard, but the preferred mechanism to
> > declare
> > variable-length types such as these ones is a flexible array
> > member[1][2],
> > introduced in C99:
> >
> > struct foo {
> > int stuff;
> > struct boo array[];
> > };
>
> Saeed, I'm expecting you to take this and the mlx4 patch via your
> trees.
Yes for the mlx5 patch, but usually Dave takes mlx4 patches directly.
since the volume of mlx4 patches is very small, let's apply them
directly to net-next, unless you want me to handle them from now on and
make your life easier, then i don't have any issue with that.
Saeed.
next prev parent reply other threads:[~2020-05-09 23:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 18:59 [PATCH] net/mlx5: Replace zero-length array with flexible-array Gustavo A. R. Silva
2020-05-08 23:36 ` Jakub Kicinski
2020-05-09 23:43 ` Saeed Mahameed [this message]
2020-05-10 3:53 ` Jakub Kicinski
2020-05-10 3:50 ` Saeed Mahameed
2020-05-11 1:06 ` Saeed Mahameed
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=fb46eb601f979d5d8d95ec5749ae06c1bc86d469.camel@mellanox.com \
--to=saeedm@mellanox.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.