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:	Thu, 23 Jul 2009 11:40:02 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	robert.w.love@...el.com
Cc:	jeffrey.t.kirsher@...el.com, linux-scsi@...r.kernel.org,
	netdev@...r.kernel.org, gospo@...hat.com, devel@...n-fcoe.org
Subject: Re: [Open-FCoE] [net-next-2.6 PATCH 5/5] fcoe: Use
 NETIF_F_FCOE_MTU flag to set up max frame size (lport->mfs)

From: Robert Love <robert.w.love@...el.com>
Date: Thu, 23 Jul 2009 11:27:28 -0700

> Please don't apply this patch to net-next. The other 4 patches in this
> series should be fine without it. If this patch is applied to net-next
> it means that most/all of the other fcoe features (that will go through
> linux-scsi) become dependent on this patch.
> 
> I was hoping to push the other fcoe features as-is and then push this
> patch through linux-scsi after the other 4 patches in this series had
> been merged by you.

Sure, I was just reading over this stuff.

But on the other hand, linux-scsi will be dependant upon net-next-2.6
because this patch here uses flags that will only be added there.

Therefore there has to be a dependency in one direction or another,
the question is which one works better for you FCOE guys.

The best thing to do in these situations is usually to create the
dependency and merge into the tree where most of the subsystem
specific bits (and thus developer ACKs) are needed.  And then
just occaisionally go and ask the other subsystem guys for ACKs
when necessary.

--
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