public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Yuval Mintz" <yuvalmin@broadcom•com>
To: "David Miller" <davem@davemloft•net>,
	"Michael Chan" <mchan@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 08:16:22 +0200	[thread overview]
Message-ID: <5067E3B6.8050703@broadcom.com> (raw)
In-Reply-To: <20120930.022836.251638342830809918.davem@davemloft.net>

> 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

Sorry about that - the HSI has changed which affects cnic as well as bnx2x.

A revised patch series which will advance both into the new FW will be submitted soon.

      reply	other threads:[~2012-09-30  6:44 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 ` [PATCH net-next 0/2] bnx2x: net-next FW upgrade David Miller
2012-09-30  6:16   ` Yuval Mintz [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=5067E3B6.8050703@broadcom.com \
    --to=yuvalmin@broadcom$(echo .)com \
    --cc=ariele@broadcom$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=eilong@broadcom$(echo .)com \
    --cc=mchan@broadcom$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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