From: Leon Romanovsky <leon@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: mlx5-next 2023-01-24 V2
Date: Thu, 2 Feb 2023 09:46:11 +0200 [thread overview]
Message-ID: <Y9tqQ0RgUtDhiVsH@unreal> (raw)
In-Reply-To: <20230126230815.224239-1-saeed@kernel.org>
On Thu, Jan 26, 2023 at 03:08:15PM -0800, Saeed Mahameed wrote:
> Hi,
>
> This pulls mlx5-next branch which includes changes from [1]:
>
> 1) From Jiri: fixe a deadlock in mlx5_ib's netdev notifier unregister.
> 2) From Mark and Patrisious: add IPsec RoCEv2 support.
>
> [1] https://lore.kernel.org/netdev/20230105041756.677120-1-saeed@kernel.org/
>
> Please pull into net-next and rdma-next.
Hi,
I don't see it in net-next yet, can you please pull it?
There are outstanding RDMA patches which depend on this shared branch.
https://lore.kernel.org/all/cover.1673960981.git.leon@kernel.org
Thanks
next prev parent reply other threads:[~2023-02-02 7:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 23:08 pull-request: mlx5-next 2023-01-24 V2 Saeed Mahameed
2023-02-02 7:46 ` Leon Romanovsky [this message]
2023-02-02 17:13 ` Jakub Kicinski
2023-02-02 17:14 ` Jason Gunthorpe
2023-02-02 17:25 ` Jakub Kicinski
2023-02-02 17:44 ` Jason Gunthorpe
2023-02-02 17:54 ` Jakub Kicinski
2023-02-02 18:03 ` Leon Romanovsky
2023-02-02 18:15 ` Saeed Mahameed
2023-02-02 18:30 ` Jakub Kicinski
2023-02-03 20:05 ` Saeed Mahameed
2023-02-03 21:14 ` Jakub Kicinski
2023-02-04 0:18 ` Jason Gunthorpe
2023-02-04 1:45 ` Jakub Kicinski
2023-02-06 14:58 ` Jason Gunthorpe
2023-02-07 0:38 ` Jakub Kicinski
2023-02-07 19:52 ` Jason Gunthorpe
2023-02-07 22:03 ` Jakub Kicinski
2023-02-08 9:17 ` Leon Romanovsky
2023-02-08 16:13 ` Jason Gunthorpe
2023-02-08 23:19 ` Jakub Kicinski
2023-02-09 0:27 ` Jason Gunthorpe
2023-02-09 0:48 ` Jakub Kicinski
2023-02-09 0:59 ` Jason Gunthorpe
2023-02-09 1:16 ` Jakub Kicinski
2023-02-10 17:15 ` Jason Gunthorpe
2023-02-09 0:36 ` Saeed Mahameed
2023-02-09 0:52 ` Jakub Kicinski
2023-02-04 0:47 ` Saeed Mahameed
2023-02-04 1:57 ` Jakub Kicinski
2023-02-05 10:26 ` Leon Romanovsky
2023-02-02 18:07 ` Leon Romanovsky
2023-02-03 20:14 ` Saeed Mahameed
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=Y9tqQ0RgUtDhiVsH@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.