From: David Miller <davem@davemloft.net>
To: robert.w.love@intel.com
Cc: jeffrey.t.kirsher@intel.com, linux-scsi@vger.kernel.org,
netdev@vger.kernel.org, gospo@redhat.com, devel@open-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)
Date: Thu, 23 Jul 2009 11:40:02 -0700 (PDT) [thread overview]
Message-ID: <20090723.114002.51085260.davem@davemloft.net> (raw)
In-Reply-To: <1248373648.23392.24.camel@fritz>
From: Robert Love <robert.w.love@intel.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.
next prev parent reply other threads:[~2009-07-23 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 23:28 [net-next-2.6 PATCH 1/5] vlan: adds fcoe offload related net_device_ops and updates fcoe_ddp_xid field Jeff Kirsher
[not found] ` <20090722232759.26937.78765.stgit-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2009-07-22 23:28 ` [net-next-2.6 PATCH 2/5] ixgbe: updates vlan feature flags to enable FCoE offloads on vlan interface Jeff Kirsher
2009-07-22 23:29 ` [net-next-2.6 PATCH 3/5] net: Add NETIF_F_FCOE_MTU to indicate support for a different MTU for FCoE Jeff Kirsher
2009-07-22 23:29 ` [net-next-2.6 PATCH 4/5] ixgbe: Add support for NETIF_F_FCOE_MTU to 82599 devices Jeff Kirsher
2009-07-22 23:29 ` [net-next-2.6 PATCH 5/5] fcoe: Use NETIF_F_FCOE_MTU flag to set up max frame size (lport->mfs) Jeff Kirsher
2009-07-23 18:27 ` [Open-FCoE] " Robert Love
2009-07-23 18:40 ` David Miller [this message]
[not found] ` <20090723.114002.51085260.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-07-23 18:48 ` Robert Love
2009-07-26 16:44 ` David Miller
[not found] ` <20090726.094402.38463748.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-07-27 16:44 ` Zou, Yi
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=20090723.114002.51085260.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@open-fcoe.org \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robert.w.love@intel.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).