From: Stan Bubrouski <stan@ccs.neu.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: res0g1ta@verizon.net
Subject: Re: [Fwd: ACPI unbug report]
Date: Sat, 20 Dec 2003 15:52:26 -0500 [thread overview]
Message-ID: <1071953546.1286.52.camel@duergar> (raw)
In-Reply-To: <3FE4037B.7090907@verizon.net>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Sat, 2003-12-20 at 03:08, RunNHide wrote:
> Thought I'd forward this on - this is NOT a bug report
>
> RunNHide
> From: ' ' <tint14@hotmail.com>
> To: res0g1ta@verizon.net
> Subject: ACPI unbug report
> Date: Sat, 20 Dec 2003 08:05:29 +0000
>
> I heard that ACPI currently isn't working in 2.6, and it seems to be working
> fine for me, so I thought this report might be helpful.
>
Well it may not work for some people, and there are quite a few open
bugs, but for majority of people with non-broken BIOS and even some that
are broken, ACPI works just fine. I don't think this kind of report is
necessary, just added traffic.
-sb
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-12-20 20:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 8:08 [Fwd: ACPI unbug report] RunNHide
2003-12-20 20:52 ` Stan Bubrouski [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=1071953546.1286.52.camel@duergar \
--to=stan@ccs.neu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=res0g1ta@verizon.net \
/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