From: Jeff Garzik <jgarzik@pobox.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [PATCH] 2.6.1 tg3 DMA engine test failure
Date: Sat, 24 Jan 2004 20:53:29 -0500 [thread overview]
Message-ID: <40132199.9090200@pobox.com> (raw)
In-Reply-To: <20040125014859.GD16272@colo.lackof.org>
Grant Grundler wrote:
> On Sat, Jan 24, 2004 at 04:15:29PM -0500, Jeff Garzik wrote:
>
>>David,
>>
>>There were two separate components to Grant's patch (hint ggg... split
>>up your patches).
>
>
> you are right - sorry.
> I'll break it down when I submit patches for RHEL3/ia64.
> (Actually, I'll only submit the changes david accepted).
>
> I had already rejected some other issues broadcom wanted me to address.
Hey, feel free to address as many issues as you would like! :)
>>What do you think about GRC-resets-sub-components part?
>>That appears valid (and probably wise) to me, but correct me if I'm wrong...
>
>
> BTW, next on the horizon is removing FTQ reset.
> I'm told the FTQ reset is NOT performed by the Tru64 (Alpha/Unix) driver
> and Broadcom is testing that with the next release of bcm5700 now.
We just went through this with Broadcom, when David applied fixes
related to ASF... rather than what Broadcom is _testing_, though, I'm
more interested to know if GRC resets FTQ's according to the hardware
engineers?
Jeff
next prev parent reply other threads:[~2004-01-25 1:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 1:36 [PATCH] 2.6.1 tg3 DMA engine test failure Grant Grundler
2004-01-24 5:00 ` David S. Miller
2004-01-24 7:30 ` Grant Grundler
2004-01-24 7:32 ` David S. Miller
2004-01-24 21:15 ` Jeff Garzik
2004-01-24 21:14 ` David S. Miller
2004-01-25 1:48 ` Grant Grundler
2004-01-25 1:53 ` Jeff Garzik [this message]
2004-01-25 5:31 ` Grant Grundler
2004-01-25 7:11 ` David S. Miller
2004-01-25 2:13 ` Grant Grundler
2004-01-26 7:52 ` David S. 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=40132199.9090200@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=grundler@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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