From: David Miller <davem@davemloft.net>
To: yuvalmin@broadcom.com
Cc: netdev@vger.kernel.org, eilong@broadcom.com, ariele@broadcom.com
Subject: Re: [PATCH net-next 0/2] bnx2x: net-next FW upgrade
Date: Sun, 30 Sep 2012 02:28:36 -0400 (EDT) [thread overview]
Message-ID: <20120930.022836.251638342830809918.davem@davemloft.net> (raw)
In-Reply-To: <1348757936-10262-1-git-send-email-yuvalmin@broadcom.com>
From: "Yuval Mintz" <yuvalmin@broadcom.com>
Date: Thu, 27 Sep 2012 16:58:54 +0200
> This series contains 2 patches - the first allows the bnx2x driver to
> utilize the recently submitted bnx2x FW 7.8.2, while the second advances
> the bnx2x version to 1.78.00-0.
>
> Please consider applying these patches to 'net-next'.
These patches do not build.
drivers/net/ethernet/broadcom/cnic.c: In function ‘cnic_init_bnx2x_tx_ring’:
drivers/net/ethernet/broadcom/cnic.c:4904:4: error: ‘ETH_TX_START_BD_ETH_ADDR_TYPE_SHIFT’ undeclared (first use in this function)
drivers/net/ethernet/broadcom/cnic.c:4904:4: note: each undeclared identifier is reported only once for each function it appears in
make[4]: *** [drivers/net/ethernet/broadcom/cnic.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [drivers/net/ethernet/broadcom] Error 2
make[2]: *** [drivers/net/ethernet] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
next prev parent reply other threads:[~2012-09-30 6:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:58 [PATCH net-next 0/2] bnx2x: net-next FW upgrade Yuval Mintz
2012-09-27 14:58 ` [PATCH net-next 1/2] bnx2x: use FW 7.8.2 Yuval Mintz
2012-09-27 14:58 ` [PATCH net-next 2/2] bnx2x: Update version to 1.78.00-0 Yuval Mintz
2012-09-30 6:28 ` David Miller [this message]
2012-09-30 6:16 ` [PATCH net-next 0/2] bnx2x: net-next FW upgrade Yuval Mintz
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=20120930.022836.251638342830809918.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariele@broadcom.com \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=yuvalmin@broadcom.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).