From: David Woodhouse <dwmw2@infradead.org>
To: David Miller <davem@davemloft.net>
Cc: mchan@broadcom.com, vladz@broadcom.com, bprakash@broadcom.com,
eilong@broadcom.com, netdev@vger.kernel.org, dmitry@broadcom.com,
yaniv.rosner@broadcom.com
Subject: Re: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx
Date: Tue, 14 Jun 2011 19:52:21 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.02.1106141952070.8326@localhost6.localdomain6> (raw)
In-Reply-To: <20110614.134653.607599293786464713.davem@davemloft.net>
On Tue, 14 Jun 2011, David Miller wrote:
> > When David Woodhouse integrates the firmware and a new firmware rpm is
> > made available for users, then the new driver will work.
Tarballs are made daily, as soon as the firmware is submitted (which
doesn't have to wait until the driver is patched). There is no issue with
bisecting, because any ABI change in the firmware means a *new* firmware
file which can be instslled in *parallel*.
> This is terrible.
Nonsense. It just means you want to be using an up-to-date copy of the
firmware, which is hardly a problem.
--
dwmw2
next prev parent reply other threads:[~2011-06-14 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201106141213.34576.vladz@broadcom.com>
[not found] ` <BD3F7F1EFBA6D54DB056C4FFA451400809D2C13864@SJEXCHCCR01.corp.ad.broadcom.com>
2011-06-14 11:32 ` [PATCH net-next 0/24] bnx2x: New FW and support for 578xx Vlad Zolotarov
2011-06-14 15:54 ` David Miller
2011-06-14 16:22 ` Vlad Zolotarov
2011-06-14 17:32 ` David Miller
2011-06-14 17:35 ` Michael Chan
2011-06-14 17:46 ` David Miller
2011-06-14 18:32 ` Vladislav Zolotarov
2011-06-14 18:33 ` David Miller
2011-06-14 19:23 ` David Woodhouse
2011-06-14 18:52 ` David Woodhouse [this message]
2011-07-18 9:48 ` Eric Dumazet
2011-07-18 9:55 ` Eilon Greenstein
2011-07-18 10:09 ` Eric Dumazet
2011-06-15 15:09 ` David Miller
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=alpine.LFD.2.02.1106141952070.8326@localhost6.localdomain6 \
--to=dwmw2@infradead.org \
--cc=bprakash@broadcom.com \
--cc=davem@davemloft.net \
--cc=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vladz@broadcom.com \
--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