From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: mchan@broadcom.com, netdev@vger.kernel.org, barak@broadcom.com,
eilong@broadcom.com
Subject: Re: [PATCH net-next 4/4 v3] bnx2x, cnic: support DRV_INFO upon FW request
Date: Tue, 06 Dec 2011 20:45:21 +0100 [thread overview]
Message-ID: <1323200721.2690.22.camel@edumazet-laptop> (raw)
In-Reply-To: <20111206.130654.1235461360535098349.davem@davemloft.net>
Le mardi 06 décembre 2011 à 13:06 -0500, David Miller a écrit :
> From: "Michael Chan" <mchan@broadcom.com>
> Date: Tue, 6 Dec 2011 00:41:50 -0800
>
> > From: Barak Witkowski <barak@broadcom.com>
> >
> > Add support to send driver capabilities, settings and statistics to
> > management firmware.
> >
> > [ Redone using many local variables, removed many unnecessary inlines,
> > and put #defines at the left margin suggested by Joe Perches ]
> >
> > Signed-off-by: Barak Witkowski <barak@broadcom.com>
> > Signed-off-by: Eilon Greenstein <eilong@broadcom.com>
> > Signed-off-by: Eddie Wai <eddie.wai@broadcom.com>
> > Signed-off-by: Michael Chan <mchan@broadcom.com>
>
> Applied.
Build error here if :
# grep CNIC .config
# CONFIG_CNIC is not set
# CONFIG_QLCNIC is not set
CC [M] drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.o
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c: In function
‘bnx2x_drv_info_fcoe_stat’:
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c:2950:33: erreur:
‘struct bnx2x’ has no member named ‘fip_mac’
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c: In function
‘bnx2x_drv_info_iscsi_stat’:
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c:3041:34: erreur:
‘struct bnx2x’ has no member named ‘cnic_eth_dev’
next prev parent reply other threads:[~2011-12-06 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 8:41 [PATCH net-next 4/4 v3] bnx2x, cnic: support DRV_INFO upon FW request Michael Chan
2011-12-06 18:06 ` David Miller
2011-12-06 19:45 ` Eric Dumazet [this message]
2011-12-06 20:15 ` Michael Chan
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=1323200721.2690.22.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=barak@broadcom.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=mchan@broadcom.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