From: Ben Hutchings <ben@decadent.org.uk>
To: barak@broadcom.com
Cc: David Woodhouse <dwmw2@infradead.org>, netdev@vger.kernel.org
Subject: Re: [PATCH linux-firmware 0/1] bnx2x: adding fw 7.2.16
Date: Sun, 19 Feb 2012 01:10:10 +0000 [thread overview]
Message-ID: <1329613810.3258.46.camel@deadeye> (raw)
In-Reply-To: <1329397677.13643.13.camel@lb-tlvb-barak.il.broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
On Thu, 2012-02-16 at 15:07 +0200, Barak Witkowski wrote:
> Hi,
>
> This patch series is actually only a single patch, but since it is too
> big for the mailing list, you can also find it at the following link:
> http://linux.broadcom.com/eilong/FW-7.2.16.0/
[...]
Applied, thanks. And thanks especially for the detailed changelog.
Ben.
--
Ben Hutchings
Every program is either trivial or else contains at least one bug
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-02-19 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 13:07 [PATCH linux-firmware 0/1] bnx2x: adding fw 7.2.16 Barak Witkowski
2012-02-19 1:10 ` 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=1329613810.3258.46.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=barak@broadcom.com \
--cc=dwmw2@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).