[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a6ca622e-9203-e69c-8d34-22e151529f0a@mellanox.com>
Date: Thu, 2 May 2019 08:45:02 +0000
From: Tal Gilboa <talgi@...lanox.com>
To: Jason Gunthorpe <jgg@...pe.ca>
CC: "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
Yishai Hadas <yishaih@...lanox.com>,
Leon Romanovsky <leon@...nel.org>,
Doug Ledford <dledford@...hat.com>,
Tariq Toukan <tariqt@...lanox.com>,
Saeed Mahameed <saeedm@...lanox.com>,
Idan Burstein <idanb@...lanox.com>,
Yamin Friedman <yaminf@...lanox.com>,
Max Gurtovoy <maxg@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH rdma-for-next 0/9] drivers/infiniband: Introduce rdma_dim
On 5/1/2019 7:04 PM, Jason Gunthorpe wrote:
>
> A lot of this is touching netdev, why wasn't netdev cc'd?
>
> Who is supposed to merge this?
>
> I think you need to take two steps and have netdev merge the above
> part and then send the single patch to RDMA for the last part, I don't
> really want to take so much netdev code here.
Ok, I'll submit the first 7 patches to netdev and the 2 RDMA specific
patches will be submitted on top of them.
>
> The maintainers file should also have some indication which tree
> patches for lib/dim/* this should go through..
>
> Jason
>
Powered by blists - more mailing lists