From: Saeed Mahameed <saeedm@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Changcheng Liu <changchengx.liu@outlook.com>,
linux-rdma@vger.kernel.org, linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net/mlx5: correct ECE offset in query qp output
Date: Mon, 9 May 2022 23:06:19 -0700 [thread overview]
Message-ID: <20220510060619.hmuwrwgplnhlfcnc@sx1> (raw)
In-Reply-To: <Ym+/WnWceotzny4f@unreal>
On 02 May 14:24, Leon Romanovsky wrote:
>On Tue, Apr 26, 2022 at 10:06:11PM +0800, Changcheng Liu wrote:
>>
>> From cd2890fc0f756d809f684768fabb34b449df6d29 Mon Sep 17 00:00:00 2001
>> From: Changcheng Liu <jerrliu@nvidia.com>
>> Date: Tue, 26 Apr 2022 21:28:14 +0800
>> Subject: [PATCH] net/mlx5: correct ECE offset in query qp output
>>
Patches withtout a target branch [net] or [net-next] are invisible to
netdev patchwork, please for next time add a target branch to the title.
>> ECE field should be after opt_param_mask in query qp output.
>>
>> Fixes: 6b646a7e4af6 ("net/mlx5: Add ability to read and write ECE options")
>> Signed-off-by: Changcheng Liu <jerrliu@nvidia.com>
>
>Saeed,
>
>Do you plan to add new patches to mlx5-next?
>This change can go to that branch as this field is not used in current
>code at all.
>
I don't mind, i will apply to net-next-mlx5, and keep it there until the end of
this release until i am sure it introduces no conflicts,
I don't see any point of putting this in mlx5-next at this time.
prev parent reply other threads:[~2022-05-10 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OSZP286MB1629E3E8563657C551711194FEFB9@OSZP286MB1629.JPNP286.PROD.OUTLOOK.COM>
2022-05-02 11:24 ` [PATCH] net/mlx5: correct ECE offset in query qp output Leon Romanovsky
2022-05-10 6:06 ` 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=20220510060619.hmuwrwgplnhlfcnc@sx1 \
--to=saeedm@nvidia.com \
--cc=changchengx.liu@outlook.com \
--cc=leon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox