From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Zhu Yanjun <yanjun.zhu@linux.dev>,
linux-rdma@vger.kernel.org, lirongqing <lirongqing@baidu.com>
Subject: Re: [PATCH v2] RDMA/mlx5: Use DEFINE_RAW_FLEX for leftovers flow attributes
Date: Wed, 23 Sep 2026 08:44:56 -0400 [thread overview]
Message-ID: <179016749674.3411706.6732193292368310779.b4-ty@kernel.org> (raw)
In-Reply-To: <20260918092337.2338-1-lirongqing@baidu.com>
On Fri, 18 Sep 2026 17:23:37 +0800, lirongqing wrote:
> Commit e91fb8b9d0ed ("RDMA/mlx5: Avoid flexible array warning") split
> the leftovers_specs[] array into two separate structs to silence the
> sparse "array of flexible structures" warning, but in doing so reversed
> the member order: eth_flow was placed before flow_attr.
>
> _create_flow_rule() locates the flow specs with:
>
> [...]
Applied, thanks!
[1/1] RDMA/mlx5: Use DEFINE_RAW_FLEX for leftovers flow attributes
https://git.kernel.org/rdma/rdma/c/e43913aabd35ee
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2026-09-23 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 9:23 [PATCH v2] RDMA/mlx5: Use DEFINE_RAW_FLEX for leftovers flow attributes lirongqing
2026-09-18 9:37 ` sashiko-bot
2026-09-23 12:44 ` 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=179016749674.3411706.6732193292368310779.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=yanjun.zhu@linux.dev \
/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