From: David Miller <davem@davemloft.net>
To: cleech@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] vlan: conditional inclusion of FCoE hooks to match netdevice.h and bnx2x
Date: Thu, 04 Apr 2019 17:18:51 -0700 (PDT) [thread overview]
Message-ID: <20190404.171851.2300207178008312076.davem@davemloft.net> (raw)
In-Reply-To: <20190402220612.1055433-1-cleech@redhat.com>
From: Chris Leech <cleech@redhat.com>
Date: Tue, 2 Apr 2019 15:06:12 -0700
> Way back in 3c9c36bcedd426f2be2826da43e5163de61735f7 the
> ndo_fcoe_get_wwn pointer was switched from depending on CONFIG_FCOE to
> CONFIG_LIBFCOE in order to allow building FCoE support into the bnx2x
> driver and used by bnx2fc without including the generic software fcoe
> module.
>
> But, FCoE is generally used over an 802.1q VLAN, and the implementation
> of ndo_fcoe_get_wwn in the 8021q module was not similarly changed. The
> result is that if CONFIG_FCOE is disabled, then bnz2fc cannot make a
> call to ndo_fcoe_get_wwn through the 8021q interface to the underlying
> bnx2x interface. The bnx2fc driver then falls back to a potentially
> different mapping of Ethernet MAC to Fibre Channel WWN, creating an
> incompatibility with the fabric and target configurations when compared
> to the WWNs used by pre-boot firmware and differently-configured
> kernels.
>
> So make the conditional inclusion of FCoE code in 8021q match the
> conditional inclusion in netdevice.h
>
> Signed-off-by: Chris Leech <cleech@redhat.com>
Applied, thanks Chris.
prev parent reply other threads:[~2019-04-05 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 22:06 [PATCH] vlan: conditional inclusion of FCoE hooks to match netdevice.h and bnx2x Chris Leech
2019-04-05 0:18 ` David Miller [this message]
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=20190404.171851.2300207178008312076.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cleech@redhat.com \
--cc=netdev@vger.kernel.org \
/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).