From: Joshua Kwan <joshk@triplehelix.org>
To: linux-kernel@vger.kernel.org
Cc: lcaron@apartia.fr, linux-kernel@vger.kernel.org
Subject: Re: TG3(Tigoon) & Kernel 2.4.27
Date: Tue, 24 Aug 2004 18:37:41 -0700 [thread overview]
Message-ID: <412BED65.5060709@triplehelix.org> (raw)
In-Reply-To: <20040824113407.287f0408.davem@redhat.com>
David S. Miller wrote:
> Oh on the contrary, I've never seen a call to request_firmware()
> in any copy of the tg3 driver and that's strange being that I'm
> the maintainer. :-)
>
> People, if you're going to use patched up kernels, report your
> problems to the people you got the kernel from. Thanks.
As a matter of fact this is most certainly kernel-source-2.4.27 from
Debian. This problem was recently fixed (as discussed in the mini-thread
about how CML1 blows chunks.)
For what it's worth to Google, kernel-tree-2.4.27-4 has just hit
unstable (will reach mirrors by tomorrow) and should have fixed this
problem.
Sorry for the noise caused to LKML.
--
Joshua Kwan
next prev parent reply other threads:[~2004-08-25 1:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 15:13 TG3(Tigoon) & Kernel 2.4.27 Laurent CARON
2004-08-24 16:25 ` Randy.Dunlap
2004-08-24 18:34 ` David S. Miller
2004-08-25 1:37 ` Joshua Kwan [this message]
2004-08-25 3:17 ` Randy.Dunlap
2004-08-25 4:02 ` Joshua Kwan
2004-08-25 4:45 ` Willy Tarreau
2004-08-25 6:36 ` David S. Miller
2004-08-25 7:47 ` Joshua Kwan
2004-08-25 8:34 ` Oliver Neukum
2004-08-25 19:03 ` David S. Miller
2004-08-31 1:14 ` Ryan Cumming
2004-08-31 1:33 ` David S. Miller
2004-08-31 5:05 ` Willy Tarreau
2004-08-25 7:40 ` Laurent CARON
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 22:16 Nathanael Nerode
2004-08-30 22:23 ` Jeff Garzik
2004-08-30 22:31 ` David S. Miller
2004-08-30 22:32 ` Andreas Schwab
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=412BED65.5060709@triplehelix.org \
--to=joshk@triplehelix.org \
--cc=lcaron@apartia.fr \
--cc=linux-kernel@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 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.