From: Saeed Mahameed <saeed@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH][next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings
Date: Thu, 20 Feb 2025 13:49:33 -0800 [thread overview]
Message-ID: <Z7ejbRN6kGluzVR3@x130> (raw)
In-Reply-To: <20250220102658.39df9b36@kernel.org>
On 20 Feb 10:26, Jakub Kicinski wrote:
>On Thu, 6 Feb 2025 15:07:07 +1030 Gustavo A. R. Silva wrote:>
>> Here is another alternative for this. And similarly to the struct_group_tagged()
>> change above, no struct members should be added before or after `struct
>> mlx5e_umr_wqe_hdr hdr;` in `struct mlx5e_umr_wqe`:
>
>Gustavo, could you submit this officially?
>
Can we have struct mlx5e_umr_wq_hdr defined anonymously within
mlx5e_umr_wqe? Let's avoid namespace pollution.
prev parent reply other threads:[~2025-02-20 21:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 2:57 [PATCH][next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-02-04 6:09 ` Michal Swiatkowski
2025-02-06 4:37 ` Gustavo A. R. Silva
2025-02-06 7:25 ` Tariq Toukan
2025-02-18 8:14 ` Gustavo A. R. Silva
2025-02-18 9:49 ` Tariq Toukan
2025-02-18 15:37 ` Andrew Lunn
2025-02-18 15:53 ` Tariq Toukan
2025-02-18 21:13 ` Jakub Kicinski
2025-02-19 12:14 ` Tariq Toukan
2025-02-20 1:46 ` Jakub Kicinski
2025-02-20 7:41 ` Tariq Toukan
2025-02-20 18:26 ` Jakub Kicinski
2025-02-20 21:49 ` Saeed Mahameed [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=Z7ejbRN6kGluzVR3@x130 \
--to=saeed@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/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