From: patchwork-bot+netdevbpf@kernel.org
To: Gustavo A. R. Silva <gustavoars@kernel.org>
Cc: saeedm@nvidia.com, leon@kernel.org, tariqt@nvidia.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, 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 v3][next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings
Date: Fri, 28 Feb 2025 01:29:13 +0000 [thread overview]
Message-ID: <174070615348.1621364.6459318760619423212.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <Z76HzPW1dFTLOSSy@kspp>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Feb 2025 13:47:32 +1030 you wrote:
> -Wflex-array-member-not-at-end was introduced in GCC-14, and we are
> getting ready to enable it, globally.
>
> So, in this particular case, we create a new `struct mlx5e_umr_wqe_hdr`
> to enclose the header part of flexible structure `struct mlx5e_umr_wqe`.
> This is, all the members except the flexible arrays `inline_mtts`,
> `inline_klms` and `inline_ksms` in the anonymous union. We then replace
> the header part with `struct mlx5e_umr_wqe_hdr hdr;` in `struct
> mlx5e_umr_wqe`, and change the type of the object currently causing
> trouble `umr_wqe` from `struct mlx5e_umr_wqe` to `struct
> mlx5e_umr_wqe_hdr` --this last bit gets rid of the flex-array-in-the-middle
> part and avoid the warnings.
>
> [...]
Here is the summary with links:
- [v3,next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings
https://git.kernel.org/netdev/net-next/c/bf08fd32cc55
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-02-28 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 3:17 [PATCH v3][next] net/mlx5e: Avoid a hundred -Wflex-array-member-not-at-end warnings Gustavo A. R. Silva
2025-02-26 18:49 ` Saeed Mahameed
2025-02-27 1:25 ` Jakub Kicinski
2025-02-27 22:27 ` Saeed Mahameed
2025-02-27 1:36 ` Gustavo A. R. Silva
2025-02-27 22:29 ` Saeed Mahameed
2025-02-28 1:29 ` patchwork-bot+netdevbpf [this message]
2025-02-28 1:37 ` 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=174070615348.1621364.6459318760619423212.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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;
as well as URLs for NNTP newsgroup(s).