From: Ben Hutchings <ben@decadent.org.uk>
To: barak@broadcom.com
Cc: David Woodhouse <dwmw2@infradead.org>,
netdev@vger.kernel.org, Eilon Greenstein <eilong@broadcom.com>
Subject: Re: [PATCH linux-firmware] bnx2x: adding fw 7.2.51
Date: Fri, 20 Apr 2012 02:01:59 +0100 [thread overview]
Message-ID: <1334883719.3209.233.camel@deadeye> (raw)
In-Reply-To: <1334831600.23463.9.camel@lb-tlvb-barak.il.broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Thu, 2012-04-19 at 13:33 +0300, Barak Witkowski wrote:
> This new FW adds support in AFEX mode (multifunction using vntag
> header).
> It also fixes following issues:
> 1. Theoretical bug in GRO acceleration (only if the GRO Segment Length
> is a multiple of the SGE Size). This will allow removing the
> workaround from the driver.
> 2. When a TPA aggregation is open and a packet is accepted with
> timestamp OOO, the new packet begins a new aggregation instead of
> being indicated separately.
>
> Signed-off-by: Barak Witkowski <barak@broadcom.com>
> Signed-off-by: Eilon Greenstein <eilong@broadcom.com>
> ---
> WHENCE | 3 +++
> bnx2x/bnx2x-e1-7.2.51.0.fw | Bin 0 -> 162152 bytes
> bnx2x/bnx2x-e1h-7.2.51.0.fw | Bin 0 -> 169960 bytes
> bnx2x/bnx2x-e2-7.2.51.0.fw | Bin 0 -> 295264 bytes
> 4 files changed, 3 insertions(+), 0 deletions(-)
> create mode 100644 bnx2x/bnx2x-e1-7.2.51.0.fw
> create mode 100644 bnx2x/bnx2x-e1h-7.2.51.0.fw
> create mode 100644 bnx2x/bnx2x-e2-7.2.51.0.fw
[...]
Applied, thanks.
Please note that my work on the linux-firmware repository is not related
to my job, so the correct address to use is ben@decadent.org.uk.
Ben.
--
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-04-20 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 10:33 [PATCH linux-firmware] bnx2x: adding fw 7.2.51 Barak Witkowski
2012-04-20 1:01 ` Ben Hutchings [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=1334883719.3209.233.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=barak@broadcom.com \
--cc=dwmw2@infradead.org \
--cc=eilong@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