From: David Miller <davem@davemloft.net>
To: dledford@redhat.com
Cc: saeedm@mellanox.com, netdev@vger.kernel.org,
linux-rdma@vger.kernel.org, leonro@mellanox.com
Subject: Re: [pull request][for-next 00/12] Mellanox, mlx5 IPoIB Muli Pkey support 2017-10-11,Re: [pull request][for-next 00/12] Mellanox, mlx5 IPoIB Muli Pkey support 2017-10-11
Date: Mon, 16 Oct 2017 05:45:03 +0100 (WEST) [thread overview]
Message-ID: <20171016.054503.459455425504112937.davem@davemloft.net> (raw)
In-Reply-To: <af28440c-bb1c-c47b-92dd-60bfbeaa839d@redhat.com>
From: Doug Ledford <dledford@redhat.com>
Date: Sat, 14 Oct 2017 17:19:34 -0400
> On 10/14/2017 2:48 PM, Saeed Mahameed wrote:
>> Hi Dave and Doug,
>>
>> This series includes updates for mlx5 IPoIB offloading driver from Alex
>> and Feras to add the support for Muli Pkey in the mlx5i ipoib offloading netdev,
>> to be merged into net-next and rdma-next trees.
>
> As far as the two IPoIB patches are concerned, they're fine.
>
>> Doug, I am sorry I couldn't base this on rc2 since the series needs and conflicts
>> with a fix that was submitted to rc3, so to keep things simple I based it on rc4,
>> I hope this is ok with you..
>
> No worries, it just means I have to submit it under another branch. But
> I'm already holding one patch series in a stand alone branch, so no big
> deal. And, actually, the IPoIB changes are so small they can simply go
> through Dave's tree if you don't have any dependent code in the IPoIB
> driver to submit after this but still in this devel cycle.
>
>> Please pull and let me know if there's any problem.
>
> Once I hear that Dave is OK with the net changes, I'm ready to pull (if
> I need to).
They look fine and I've pulled this into net-next.
Thanks.
next prev parent reply other threads:[~2017-10-16 4:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 18:48 [pull request][for-next 00/12] Mellanox, mlx5 IPoIB Muli Pkey support 2017-10-11 Saeed Mahameed
2017-10-14 18:48 ` [for-next 02/12] net/mlx5: PTP code migration to driver core section Saeed Mahameed
2017-10-14 18:48 ` [for-next 04/12] net/mlx5: Support for attaching multiple underlay QPs to root flow table Saeed Mahameed
2017-10-14 18:48 ` [for-next 05/12] IB/ipoib: Grab rtnl lock on heavy flush when calling ndo_open/stop Saeed Mahameed
2017-10-14 18:48 ` [for-next 06/12] IB/ipoib: Add ability to set PKEY index to lower device driver Saeed Mahameed
2017-10-14 18:48 ` [for-next 07/12] net/mlx5e: IPoIB, Support for setting PKEY index to underlay QP Saeed Mahameed
2017-10-14 18:48 ` [for-next 09/12] net/mlx5e: IPoIB, Add PKEY child interface nic profile Saeed Mahameed
2017-10-14 18:48 ` [for-next 10/12] net/mlx5e: IPoIB, Add PKEY child interface ndos Saeed Mahameed
[not found] ` <20171014184827.18491-1-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-10-14 18:48 ` [for-next 01/12] net/mlx5: File renaming towards ptp core implementation Saeed Mahameed
2017-10-14 18:48 ` [for-next 03/12] net/mlx5e: IPoIB, Move underlay QP init/uninit to separate functions Saeed Mahameed
2017-10-14 18:48 ` [for-next 08/12] net/mlx5e: IPoIB, Use hash-table to map between QPN to child netdev Saeed Mahameed
[not found] ` <20171014184827.18491-9-saeedm-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-10-23 15:47 ` Jason Gunthorpe
2017-10-24 6:28 ` Alex Vesker
2017-10-14 18:48 ` [for-next 11/12] net/mlx5e: IPoIB, Add PKEY child interface ethtool ops Saeed Mahameed
2017-10-14 21:19 ` [pull request][for-next 00/12] Mellanox, mlx5 IPoIB Muli Pkey support 2017-10-11 Doug Ledford
2017-10-15 6:30 ` Leon Romanovsky
2017-10-16 4:45 ` David Miller [this message]
[not found] ` <20171016.054503.459455425504112937.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2017-10-18 15:08 ` [pull request][for-next 00/12] Mellanox, mlx5 IPoIB Muli Pkey support 2017-10-11,Re: " Doug Ledford
2017-10-14 18:48 ` [for-next 12/12] net/mlx5e: IPoIB, Modify rdma netdev allocate and free to support PKEY Saeed Mahameed
2017-10-14 22:51 ` [pull request][for-next 00/12] Mellanox, mlx5 IPoIB Muli Pkey support 2017-10-11 Parav Pandit
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=20171016.054503.459455425504112937.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--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).