From: Jason Gunthorpe <jgg@mellanox•com>
To: Leon Romanovsky <leon@kernel•org>
Cc: Doug Ledford <dledford@redhat•com>,
Yishai Hadas <yishaih@mellanox•com>,
RDMA mailing list <linux-rdma@vger•kernel.org>,
Artemy Kovalyov <artemyko@mellanox•com>,
Moni Shoua <monis@mellanox•com>,
Saeed Mahameed <saeedm@mellanox•com>,
linux-netdev <netdev@vger•kernel.org>,
Leon Romanovsky <leonro@mellanox•com>
Subject: Re: [PATCH mlx5-next] net/mlx5: Fix DCT creation bad flow
Date: Wed, 6 Mar 2019 18:52:16 +0000 [thread overview]
Message-ID: <20190306185212.GQ1758@mellanox.com> (raw)
In-Reply-To: <20190306172050.20033-1-leon@kernel.org>
On Wed, Mar 06, 2019 at 07:20:50PM +0200, Leon Romanovsky wrote:
> From: Yishai Hadas <yishaih@mellanox•com>
>
> In case the DCT creation command has succeeded a DRAIN must be issued
> before calling DESTROY.
>
> In addition, the original code used the wrong parameter for the DESTROY
> command, 'in' instead of 'din', which caused another creation try
> instead of destroying.
>
> Cc: <stable@vger•kernel.org> # 4.15
> Fixes: 57cda166bbe0 ("net/mlx5: Add DCT command interface")
> Signed-off-by: Yishai Hadas <yishaih@mellanox•com>
> Reviewed-by: Artemy Kovalyov <artemyko@mellanox•com>
> Signed-off-by: Leon Romanovsky <leonro@mellanox•com>
> Jason, Doug
>
> If it is possible, I would like to take this patch too:
> https://patchwork.kernel.org/patch/10828299/
This should have been applied to the shared tree though??
It is RDMA focused, do you want it to go to the RDMA tree?
Jason
next prev parent reply other threads:[~2019-03-06 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 17:20 [PATCH mlx5-next] net/mlx5: Fix DCT creation bad flow Leon Romanovsky
2019-03-06 18:52 ` Jason Gunthorpe [this message]
2019-03-06 18:57 ` Leon Romanovsky
2019-03-12 18:09 ` Jason Gunthorpe
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=20190306185212.GQ1758@mellanox.com \
--to=jgg@mellanox$(echo .)com \
--cc=artemyko@mellanox$(echo .)com \
--cc=dledford@redhat$(echo .)com \
--cc=leon@kernel$(echo .)org \
--cc=leonro@mellanox$(echo .)com \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=monis@mellanox$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=saeedm@mellanox$(echo .)com \
--cc=yishaih@mellanox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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