From: Joseph Pingenot <trelane@digitasaru.net>
To: Len Brown <len.brown@intel.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ACPI breakage in 2.6.2-rc3 (and before)
Date: Mon, 2 Feb 2004 18:07:36 -0600 [thread overview]
Message-ID: <20040203000732.GA6376@digitasaru.net> (raw)
In-Reply-To: <1075664452.2394.5.camel@dhcppc4>
>From Len Brown on Sunday, 01 February, 2004:
>Joseph,
>Please try this patch
>http://bugzilla.kernel.org/attachment.cgi?id=1965&action=view
>from this bug report:
>http://bugzilla.kernel.org/show_bug.cgi?id=1766
>It should be in the next mm patch, and if it causes no regression will
>be pushed to 2.6.2.
>thanks,
>-Len
Patch works! I just applied and tested, and it worked great.
What magic does that patch work?
Thanks!
-Joseph
>On Sun, 2004-02-01 at 15:19, Joseph Pingenot wrote:
>> From Linus Torvalds on Friday, 30 January, 2004:
>> >The bulk of this is an ACPI update, but there's USB, ia-64, i2c, XFS
>> and
>> >PCI hotplug updates here too.
>> >Please don't send in anything but critical fixes until after the
>> final
>> >2.6.2 release.
>> Hmm. I just tried 2.6.2-rc3 (after having tried 2.6.1 after having
>> tried 2.6.2-rc2-mm1), and I note that ACPI can get my battery
>> status in 2.6.1, but *not* in 2.6.2-rc2-mm1 or in 2.6.2-rc3.
>> It notes that there is a battery in one of the two bays, and
>> that it's on battery or AC power, but nothing more; all status
>> readouts say that the battery's drained.
>> System is a Dell Inspiron 8600.
>> Thanks!
next prev parent reply other threads:[~2004-02-03 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEAEA@hdsmsx402.hd.intel.com>
2004-02-01 19:40 ` Len Brown
2004-02-03 0:07 ` Joseph Pingenot [this message]
2004-01-31 2:27 Linux 2.6.2-rc3 Linus Torvalds
2004-02-01 20:19 ` ACPI breakage in 2.6.2-rc3 (and before) Joseph Pingenot
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=20040203000732.GA6376@digitasaru.net \
--to=trelane@digitasaru.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome