All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bhanu Prakash Gollapudi" <bprakash@broadcom.com>
To: "Randy Dunlap" <rdunlap@xenotime.net>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"robert.w.love@intel.com" <robert.w.love@intel.com>,
	"devel@open-fcoe.org" <devel@open-fcoe.org>
Subject: Re: linux-next: Tree for Aug 25
Date: Fri, 26 Aug 2011 09:42:20 -0700	[thread overview]
Message-ID: <4E57CCEC.9060000@broadcom.com> (raw)
In-Reply-To: <885a6d6210a7d4c56601380f146e7ba9.squirrel@xenotime.net>

On 8/26/2011 12:26 AM, Randy Dunlap wrote:
>
> On Wed, August 24, 2011 11:35 pm, Stephen Rothwell wrote:
>> Hi all,
>>
>> The powerpc allyesconfig build still fails today.
>
>
> CONFIG_FCOE is not enabled:
>
> drivers/scsi/bnx2fc/bnx2fc_fcoe.c: In function 'bnx2fc_net_config':
> drivers/scsi/bnx2fc/bnx2fc_fcoe.c:765: error: 'NETDEV_FCOE_WWNN'
> undeclared (first use in this function)
> drivers/scsi/bnx2fc/bnx2fc_fcoe.c:771: error: 'NETDEV_FCOE_WWPN'
> undeclared (first use in this function)
>
>
> Maybe this driver should select FCOE?
bnx2fc does not depend on FCOE. Instead both fcoe and bnx2fc drivers 
depend on LIBFCOE.  So, I'll modify to access 
NETDEV_FCOE_WWNN/NETDEV_FCOE_WWPN when CONFIG_LIBFCOE  is enabled.

Patch will be submitted soon.

Thanks,
Bhanu
>
> ~Randy
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



  reply	other threads:[~2011-08-26 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  6:35 linux-next: Tree for Aug 25 Stephen Rothwell
2011-08-26  7:26 ` Randy Dunlap
2011-08-26 16:42   ` Bhanu Prakash Gollapudi [this message]
2011-08-26 16:59     ` Zou, Yi
2014-08-25  4:51 Stephen Rothwell
2014-08-25  5:21 ` Guenter Roeck
2015-08-25  8:32 Stephen Rothwell
2016-08-25  4:54 Stephen Rothwell
2016-08-25  5:02 ` Stephen Rothwell
2017-08-25  8:42 Stephen Rothwell
2020-08-25  8:19 Stephen Rothwell
2021-08-25  9:43 Stephen Rothwell
2022-08-25  5:44 Stephen Rothwell
2023-08-25  5:52 Stephen Rothwell

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=4E57CCEC.9060000@broadcom.com \
    --to=bprakash@broadcom.com \
    --cc=devel@open-fcoe.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=robert.w.love@intel.com \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.