linux-kernel - Re: linux rdma 3.14 merge plans

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 05 Mar 2014 11:03:38 -0800
From:	"Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To:	Roland Dreier <roland@...nel.org>
Cc:	Or Gerlitz <or.gerlitz@...il.com>,
	Hefty Sean <sean.hefty@...el.com>,
	linux-rdma <linux-rdma@...r.kernel.org>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	target-devel <target-devel@...r.kernel.org>,
	Sagi Grimberg <sagig@...lanox.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: linux rdma 3.14 merge plans

On Wed, 2014-03-05 at 07:18 -0800, Roland Dreier wrote:
> On Wed, Mar 5, 2014 at 1:54 AM, Nicholas A. Bellinger
> <nab@...ux-iscsi.org> wrote:
> > That all said, do you have an objection wrt taking this bits through
> > target-pending..?  Given the dependencies involved, that would seem the
> > most logical path to take.
> 
> Perhaps not surprisingly, I would prefer to get a chance to review a
> major change to the core RDMA midlayer rather than having you merge it
> through your tree.  So yes I do object.  Please give me a chance to
> review and merge it.  I am working on that this week.
> 

Great.  We'll be looking for a response by the end of the week.

Otherwise if you end up not having time, we'd still like to move forward
for v3.15 given the amount of review the series has already gotten on
the list.

Thank you,

--nab



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/