From: David Woodhouse <dwmw2@infradead.org>
To: Michael Chan <mchan@broadcom.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] linux-firmware: bnx2: Update firmware and version
Date: Wed, 11 May 2011 00:27:57 +0100 [thread overview]
Message-ID: <1305070078.30435.103.camel@i7.infradead.org> (raw)
In-Reply-To: <1305069556.9029.133.camel@nseg_linux_HP1.broadcom.com>
On Tue, 2011-05-10 at 16:19 -0700, Michael Chan wrote:
> > > Update 5709 mips firmware to 6.2.1a to fix iSCSI performance
> > > regression. There was an unnecessary context read in the fast path
> > > affecting performance.
> >
> > Is this update not ABI compatible? You have changed the soname of the
> > firmware... was that intentional?
> >
>
> The firmware is tightly coupled to the driver. We only test one
> combination of driver/firmware and don't guarantee compatibility with
> other combinations.
OK, patch applied and pushed; thanks.
--
dwmw2
prev parent reply other threads:[~2011-05-10 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 22:16 [PATCH] linux-firmware: bnx2: Update firmware and version Michael Chan
2011-05-10 23:10 ` David Woodhouse
2011-05-10 23:19 ` Michael Chan
2011-05-10 23:27 ` David Woodhouse [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=1305070078.30435.103.camel@i7.infradead.org \
--to=dwmw2@infradead.org \
--cc=mchan@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;
as well as URLs for NNTP newsgroup(s).