From: Lee Revell <rlrevell@joe-job.com>
To: Roger Luethi <rl@hellgate.ch>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.8-rc4 [RESEND] via-rhine: Really call rhine_power_init()
Date: Fri, 13 Aug 2004 00:45:11 -0400 [thread overview]
Message-ID: <1092372311.3450.5.camel@mindpipe> (raw)
In-Reply-To: <20040810083350.GA23771@k3.hellgate.ch>
On Tue, 2004-08-10 at 04:33, Roger Luethi wrote:
> This is my third and last attempt to get this fix merged for 2.6.8.
>
> Without this patch, mainline via-rhine cannot wake the chip if some other
> driver puts it to D3. The problem has hit quite a few people already.
>
Argh, this is *still* not fixed in -rc4! How loud does one have to yell
to get an absolutely FATAL bug with a trivial fix merged?
Lots of people spent lots of time trying to track this bug down. I
would hate to think all that time was wasted. *Please* apply Roger's
patch, or many people will be unable to upgrade to 2.6.8. I am getting
tired of replacing via-rhine.c with the version from -mm every time I
compile a new kernel just to keep my network card working.
Lee
next prev parent reply other threads:[~2004-08-13 4:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 3:03 Linux 2.6.8-rc4 Linus Torvalds
2004-08-10 8:33 ` Linux 2.6.8-rc4 [RESEND] via-rhine: Really call rhine_power_init() Roger Luethi
2004-08-10 14:34 ` Lee Revell
2004-08-13 4:45 ` Lee Revell [this message]
2004-08-13 8:44 ` Roger Luethi
2004-08-13 15:34 ` Linus Torvalds
2004-08-13 17:40 ` Lee Revell
2004-08-13 22:06 ` Lee Revell
2004-08-16 12:45 ` Patrick McFarland
2004-08-10 17:37 ` Linux 2.6.8-rc4 (compile stats) John Cherry
2004-08-10 18:39 ` [patch] 2.6.8-rc4: compile error with gcc 2.95 Adrian Bunk
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=1092372311.3450.5.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rl@hellgate.ch \
--cc=torvalds@osdl.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