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]
Message-ID: <CAJZOPZJZYN5YfVBRrC0Z3kvDfWcU=S7vCi4UWmzre2+PxUyM=g@mail.gmail.com>
Date:	Fri, 27 Jul 2012 07:42:01 +0300
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	Roland Dreier <roland@...nel.org>
Cc:	David Miller <davem@...emloft.net>, ogerlitz@...lanox.com,
	netdev@...r.kernel.org, eric.dumazet@...il.com, cl@...ux.com,
	shlomop@...lanox.com
Subject: Re: [PATCH RESEND net-next V2] IB/ipoib: break linkage to
 neighbouring system

On Wed, Jul 25, 2012 at 10:52 AM, Roland Dreier <roland@...nel.org> wrote:
> On Tue, Jul 24, 2012 at 2:00 PM, David Miller <davem@...emloft.net> wrote:

>> Looks good, Roland you got this?

> Yes, I'll read it over and pick it up, thanks.

Hi Roland,

Just to make sure, you are picking this for 3.6, correct?

I'd like to make sure that the merge of this patch through the
infiniband tree will not introduce dependancy with the review/merge of
the Ethernet IPoIB driver that runs through netdev. If this patch
lands in 3.6-rcX, Dave will eventually pick it into net-next and we're
ok, if not, things get complicated without any real reason, makes
sense?

Or.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ