From: "Dmitry Kravkov" <dmitry@broadcom.com>
To: "Randy Dunlap" <rdunlap@xenotime.net>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
netdev <netdev@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Eilon Greenstein" <eilong@broadcom.com>
Subject: Re: linux-next: Tree for July 16 (net/bnx2x)
Date: Sat, 16 Jul 2011 23:24:02 +0300 [thread overview]
Message-ID: <1310847842.2826.1.camel@lb-tlvb-dmitry> (raw)
In-Reply-To: <20110716121427.11760128.rdunlap@xenotime.net>
On Sat, 2011-07-16 at 12:14 -0700, Randy Dunlap wrote:
> On Sun, 17 Jul 2011 00:08:15 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110707:
>
> When BCM_CNIC is not defined:
>
> drivers/net/bnx2x/bnx2x_cmn.c:1429: error: 'bp' undeclared (first use in this function)
>
> Full kernel config file is attached.
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
bnx2x: Fix compilation when CNIC is not selected in config
Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Dmitry Kravkov <dmitry@broadcom.com>
---
drivers/net/bnx2x/bnx2x_cmn.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/bnx2x/bnx2x_cmn.c
b/drivers/net/bnx2x/bnx2x_cmn.c
index e5fac62..b05ce93 100644
--- a/drivers/net/bnx2x/bnx2x_cmn.c
+++ b/drivers/net/bnx2x/bnx2x_cmn.c
@@ -1403,8 +1403,8 @@ void bnx2x_netif_stop(struct bnx2x *bp, int
disable_hw)
u16 bnx2x_select_queue(struct net_device *dev, struct sk_buff *skb)
{
-#ifdef BCM_CNIC
struct bnx2x *bp = netdev_priv(dev);
+#ifdef BCM_CNIC
if (NO_FCOE(bp))
return skb_tx_hash(dev, skb);
else {
--
1.7.2.2
next prev parent reply other threads:[~2011-07-16 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110717000815.c83755be9598d34ac8431908@canb.auug.org.au>
2011-07-16 19:14 ` linux-next: Tree for July 16 (net/bnx2x) Randy Dunlap
2011-07-16 20:24 ` Dmitry Kravkov [this message]
2011-07-16 20:26 ` David Miller
2011-07-16 20:30 ` Dmitry Kravkov
2011-07-16 20:36 ` David Miller
2011-07-16 21:01 ` Randy Dunlap
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=1310847842.2826.1.camel@lb-tlvb-dmitry \
--to=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--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 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).