From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org, Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH rdma-next] RDMA/mlx5: Avoid flexible array warning
Date: Sun, 25 May 2025 03:52:13 -0400 [thread overview]
Message-ID: <174815953380.1055957.16164106385233511019.b4-ty@kernel.org> (raw)
In-Reply-To: <7b891b96a9fc053d01284c184d25ae98d35db2d4.1747827041.git.leon@kernel.org>
On Wed, 21 May 2025 14:34:58 +0300, Leon Romanovsky wrote:
> The following warning is reported by sparse tool:
> drivers/infiniband/hw/mlx5/fs.c:1664:26: warning: array of flexible
> structures
>
> Avoid it by simply splitting array into two separate structs.
>
>
> [...]
Applied, thanks!
[1/1] RDMA/mlx5: Avoid flexible array warning
https://git.kernel.org/rdma/rdma/c/de748d531c52a5
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2025-05-25 7:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 11:34 [PATCH rdma-next] RDMA/mlx5: Avoid flexible array warning Leon Romanovsky
2025-05-21 18:27 ` Zhu Yanjun
2025-05-25 7:52 ` Leon Romanovsky [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=174815953380.1055957.16164106385233511019.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox