From: Divy Le Ray <divy@chelsio.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: pull request: linux-firmware: update cxgb* firmwares
Date: Sat, 18 Feb 2012 17:35:34 -0800 [thread overview]
Message-ID: <4F4051E6.6030603@chelsio.com> (raw)
In-Reply-To: <1329613455.3258.45.camel@deadeye>
On 2/18/2012 5:04 PM, Ben Hutchings wrote:
> On Sun, 2012-02-19 at 00:58 +0000, Ben Hutchings wrote:
>> On Fri, 2012-02-17 at 11:30 -0800, Divy Le Ray wrote:
>>> On 2/16/2012 7:41 PM, Ben Hutchings wrote:
> [...]
>>>> Are there any versions of the cxgb4 driver that will specifically
>>>> request cxgb4/t4fw-1.3.10.0.bin? If not, what's the point of keeping it
>>>> around after changing the cxgb4/t4fw.bin symlink?
>>> Hi Ben,
>>>
>>> I originally removed cxgb4/t4fw-1.3.10.0.bin when I posted the request
>>> against David's tree.
>>> Subsequent review from Neil requested to keep it around at least for a
>>> while (https://lkml.org/lkml/2012/2/11/61).
>>> Either way is fine to me.
>> No, Neil said you need to maintain cxgb4/t4fw.bin, but it's perfectly
>> fine for that to be a symlink.
> So I've pulled your changes and then deleted the cxgb4/t4fw-1.3.10.0.bin
> as a separate commit.
Than you.
Cheers,
Divy
prev parent reply other threads:[~2012-02-19 1:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 3:07 pull request: linux-firmware: update cxgb* firmwares Divy Le Ray
2012-02-11 14:07 ` Neil Horman
2012-02-13 5:52 ` Divy Le Ray
2012-02-13 11:37 ` Neil Horman
2012-02-16 7:18 ` Divy Le Ray
2012-02-17 3:41 ` Ben Hutchings
2012-02-17 19:26 ` Neil Horman
2012-02-17 19:30 ` Divy Le Ray
2012-02-19 0:58 ` Ben Hutchings
2012-02-19 1:04 ` Ben Hutchings
2012-02-19 1:35 ` Divy Le Ray [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=4F4051E6.6030603@chelsio.com \
--to=divy@chelsio.com \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.