From: Steve Wise <swise@opengridcomputing.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Divy Le Ray <divy@chelsio.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 9/11] cxgb3 - engine microcode update
Date: Wed, 05 Sep 2007 09:36:57 -0500 [thread overview]
Message-ID: <46DEBF09.5080808@opengridcomputing.com> (raw)
In-Reply-To: <20070905143029.GC19543@havoc.gtf.org>
Jeff Garzik wrote:
> On Wed, Sep 05, 2007 at 09:00:04AM -0500, Steve Wise wrote:
>>
>> Jeff Garzik wrote:
>>> Divy Le Ray wrote:
>>>> From: Divy Le Ray <divy@chelsio.com>
>>>>
>>>> Load microcode engine when the interface
>>>> is configured up.
>>>> Bump up version to 1.1.0.
>>>> Allow the driver to be and running with
>>>> older microcode images.
>>>> Allow ethtool to log the microcode version.
>>>>
>>>> Signed-off-by: Divy Le Ray <divy@chelsio.com>
>>> ACK patches 9-14, but dropped, since they do not apply to #upstream
>>> (probably due to fixes sent into 2.6.23-rc)
>>>
>> Hey Jeff,
>>
>> I think 9-14 still need to be incorporated. I don't see them in your
>> upstream branch, and they aren't in linus' tree either.
>
> I am not the blocker here. Re-read the email you quoted.
>
> Jeff, still waiting for the patches
>
Ok. I didn't get that you were stating that the patches should be
resent because they're busted :)
Steve.
next prev parent reply other threads:[~2007-09-05 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 3:49 [PATCH 9/11] cxgb3 - engine microcode update Divy Le Ray
2007-08-31 13:38 ` Jeff Garzik
2007-09-05 14:00 ` Steve Wise
2007-09-05 14:30 ` Jeff Garzik
2007-09-05 14:36 ` Steve Wise [this message]
2007-09-05 22:57 ` Divy Le Ray
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=46DEBF09.5080808@opengridcomputing.com \
--to=swise@opengridcomputing.com \
--cc=divy@chelsio.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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).