public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vlad Zolotarov" <vladz@broadcom.com>
To: "David Woodhouse" <dwmw2@infradead.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Eilon Greenstein" <eilong@broadcom.com>,
	"Dmitry Kravkov" <dmitry@broadcom.com>,
	"Yaniv Rosner" <yaniv.rosner@broadcom.com>
Subject: Re: [PATCH] linux-firmware: Add a new bnx2x FW 7.0.20.0
Date: Tue, 14 Jun 2011 12:57:40 +0300	[thread overview]
Message-ID: <201106141257.40621.vladz@broadcom.com> (raw)
In-Reply-To: <1308044887.3450.4.camel@i7.infradead.org>

On Tuesday 14 June 2011 12:48:06 David Woodhouse wrote:
> On Tue, 2011-06-14 at 12:41 +0300, Vlad Zolotarov wrote:
> > 
> >  bnx2x/bnx2x-e1-7.0.20.0.fw.ihex  |10075 +++++++++++++++++++++
> >  bnx2x/bnx2x-e1h-7.0.20.0.fw.ihex |10538 ++++++++++++++++++++++
> >  bnx2x/bnx2x-e2-7.0.20.0.fw.ihex  |18190 ++++++++++++++++++++++++++++++++++++++
> 
> You haven't tested this, have you?

What do u mean? I do have put the ihex files under the net-next kernel tree at the regular location plus I updated the the kernel's firmware/WHENCE and firmware/Makefile files and of course I ran a functionality tests for the driver after all patches and with the new firmware.

If u meant the different sort of testing, pls., clarify.

> 
> Add the binary file, not an ihex version.

I'll resend the binary files. 

thanks,
vlad

> 
> 


  reply	other threads:[~2011-06-14  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201106141241.40764.vladz@broadcom.com>
2011-06-14  9:48 ` [PATCH] linux-firmware: Add a new bnx2x FW 7.0.20.0 David Woodhouse
2011-06-14  9:57   ` Vlad Zolotarov [this message]
2011-06-14 10:04     ` David Woodhouse
2011-06-14 10:10       ` Vlad Zolotarov
2011-06-14 10:16         ` David Woodhouse
2011-06-14 10:53           ` Vlad Zolotarov

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=201106141257.40621.vladz@broadcom.com \
    --to=vladz@broadcom.com \
    --cc=dmitry@broadcom.com \
    --cc=dwmw2@infradead.org \
    --cc=eilong@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=yaniv.rosner@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