From: Parav Pandit <parav@nvidia.com>
To: Parav Pandit <parav@nvidia.com>,
"dledford@redhat.com" <dledford@redhat.com>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: "jiri@mellanox.com" <jiri@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"michaelgur@mellanox.com" <michaelgur@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: RE: [PATCH rdma-rc] RDMA/mlx5: Fix devlink deadlock on net namespace deletion
Date: Mon, 26 Oct 2020 13:47:18 +0000 [thread overview]
Message-ID: <BY5PR12MB4322960FBC4219A6DD7D37BDDC190@BY5PR12MB4322.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201026133835.22202-1-parav@nvidia.com>
> From: Parav Pandit <parav@nvidia.com>
> Sent: Monday, October 26, 2020 7:09 PM
[..]
>
> Fixes: 4383cfcc65e7 ("net/mlx5: Add devlink reload")
> Signed-off-by: Parav Pandit <parav@nvidia.com>
I missed to include Leon's signed-off and updating version here.
Sent now with correct header and signoff at [1].
[1] https://lore.kernel.org/linux-rdma/20201026134359.23150-1-parav@nvidia.com/T/#u
> ---
> Changelog:
> v0->v1:
> - updated comment for mlx5_core_net API to be used by multiple mlx5
> drivers
next prev parent reply other threads:[~2020-10-26 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 5:27 [PATCH rdma-rc] RDMA/mlx5: Fix devlink deadlock on net namespace deletion Leon Romanovsky
2020-10-19 13:07 ` Jason Gunthorpe
2020-10-19 13:23 ` Parav Pandit
2020-10-19 19:01 ` Jason Gunthorpe
2020-10-19 19:26 ` Parav Pandit
2020-10-20 11:41 ` Parav Pandit
2020-10-26 13:38 ` Parav Pandit
2020-10-26 13:47 ` Parav Pandit [this message]
2020-10-26 13:43 ` [PATCH rdma-rc RESEND v1] " Parav Pandit
2020-10-26 22:25 ` 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=BY5PR12MB4322960FBC4219A6DD7D37BDDC190@BY5PR12MB4322.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=jiri@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=michaelgur@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).