From: Doug Ledford <dledford@redhat.com>
To: Saeed Mahameed <saeedm@mellanox.com>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: Jason Gunthorpe <jgg@mellanox.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Matan Barak <matanb@mellanox.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Leon Romanovsky <leonro@mellanox.com>,
Aviad Yehezkel <aviadye@mellanox.com>,
Boris Pismenny <borisp@mellanox.com>
Subject: Re: [pull request][for-next 00/11] Mellanox, mlx5 IPSec updates 2018-02-28-2 (Part 2)
Date: Tue, 13 Mar 2018 15:52:44 -0400 [thread overview]
Message-ID: <1520970764.18703.1.camel@redhat.com> (raw)
In-Reply-To: <1520905422.18703.0.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On Mon, 2018-03-12 at 21:43 -0400, Doug Ledford wrote:
> On Mon, 2018-03-12 at 21:43 +0000, Saeed Mahameed wrote:
> > On Thu, 2018-03-08 at 14:14 -0500, Doug Ledford wrote:
> > > On 3/8/2018 1:04 PM, David Miller wrote:
> > > > From: Saeed Mahameed <saeedm@mellanox.com>
> > > > Date: Wed, 7 Mar 2018 17:26:03 -0800
> > > >
> > > > > Hi Dave and Doug,
> > > > >
> > > > > This series includes shared code updates (IPSec part2) for mlx5
> > > > > core
> > > > > driver for both netdev and rdma subsystems. This series should
> > > > > be pulled
> > > > > to both trees so we can continue netdev and rdma specific
> > > > > submissions
> > > > > separately.
> > > >
> > > > Doug, please give this series a quick review.
> > > >
> > > > Thank you.
> > > >
> > >
> > > I'm good with it. Pull it as you see fit.
> > >
> >
> > Hi Doug,
> >
> > Just FYI, I see that Dave already pulled the series into net-next.
> > I think you can pull as well, so Leon will start the mlx5 RDMA
> > submissions as planned on top this last pull request.
> >
> > thanks,
> > Saeed.
>
> Ok, thanks Saeed.
>
Pulled and a new wip/dl-for-next is available.
--
Doug Ledford <dledford@redhat.com>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-13 19:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 1:26 [pull request][for-next 00/11] Mellanox, mlx5 IPSec updates 2018-02-28-2 (Part 2) Saeed Mahameed
2018-03-08 1:26 ` [for-next 01/11] net/mlx5: Use MLX5_IPSEC_DEV macro for ipsec caps Saeed Mahameed
2018-03-08 1:26 ` [for-next 02/11] net/mlx5: IPSec, Generalize sandbox QP commands Saeed Mahameed
2018-03-08 1:26 ` [for-next 03/11] net/mlx5e: IPSec, Add support for ESP trailer removal by hardware Saeed Mahameed
2018-03-08 1:26 ` [for-next 04/11] net/mlx5: IPSec, Add command V2 support Saeed Mahameed
2018-03-08 1:26 ` [for-next 05/11] net/mlx5: Export ipsec capabilities Saeed Mahameed
2018-03-08 1:26 ` [for-next 06/11] net/mlx5: Added required metadata capability for ipsec Saeed Mahameed
2018-03-08 1:26 ` [for-next 07/11] net/mlx5: Refactor accel IPSec code Saeed Mahameed
2018-03-08 1:26 ` [for-next 08/11] net/mlx5: Add flow-steering commands for FPGA IPSec implementation Saeed Mahameed
2018-03-08 1:26 ` [for-next 09/11] net/mlx5e: Added common function for to_ipsec_sa_entry Saeed Mahameed
2018-03-08 1:26 ` [for-next 10/11] net/mlx5: IPSec, Add support for ESN Saeed Mahameed
2018-03-08 1:26 ` [for-next 11/11] net/mlx5: Fix wrongly assigned CQ reference counter Saeed Mahameed
2018-03-08 18:04 ` [pull request][for-next 00/11] Mellanox, mlx5 IPSec updates 2018-02-28-2 (Part 2) David Miller
2018-03-08 19:14 ` Doug Ledford
2018-03-08 19:38 ` Randy Dunlap
2018-03-08 19:42 ` Doug Ledford
2018-03-08 19:43 ` David Miller
2018-03-12 21:43 ` Saeed Mahameed
2018-03-13 1:43 ` Doug Ledford
2018-03-13 19:52 ` Doug Ledford [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=1520970764.18703.1.camel@redhat.com \
--to=dledford@redhat.com \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=davem@davemloft.net \
--cc=jgg@mellanox.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matanb@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.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).