From: Len Brown <len.brown@intel.com>
To: Dax Kelson <dax@gurulabs.com>
Cc: Administrator@smtp.paston.co.uk, Andrew Morton <akpm@osdl.org>,
Luming Yu <luming.yu@intel.com>,
Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>,
linux-kernel@vger.kernel.org, linux-acpi <linux-acpi@intel.com>
Subject: Re: ACPI battery problem with 2.6.1-rc1-mm2 kernel patch
Date: 29 Mar 2004 22:29:18 -0500 [thread overview]
Message-ID: <1080617358.980.30.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615F6C72@hdsmsx402.hd.intel.com>
On Mon, 2004-03-29 at 10:46, Dax Kelson wrote:
> On Mon, 2004-01-05 at 19:59, Valdis.Kletnieks@vt.edu wrote:
> > On Mon, 05 Jan 2004 18:08:59 PST, Andrew Morton said:
> >
> > > Thanks, the acpi-20031203 patch seems to have introduced a handful
> of
> > > regressions.
> >
> > As suggested by Yu Luming, the patch at
> http://bugzilla.kernel.org/show_bug.cgi?id=1766
> > is confirmed to fix my issue. 2.6.1-rc1-mm2 with that patch gives
> me:
>
> Just confirming that the same patched fixed up the battery reporting
> problems on my laptop as well.
While I'm happy that patches backported to 2.6.0 and 2.6.1
work properly, is is probably more valuable to the community
to know that the latest 2.6 release works -- particularly since
the fix in question was integrated into the baseline 6 weeks ago.
thanks,
-Len
next parent reply other threads:[~2004-03-30 3:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F6C72@hdsmsx402.hd.intel.com>
2004-03-30 3:29 ` Len Brown [this message]
2004-01-07 9:52 ACPI battery problem with 2.6.1-rc1-mm2 kernel patch Yu, Luming
-- strict thread matches above, loose matches on Subject: below --
2004-01-07 9:25 Yu, Luming
2004-01-06 1:53 Jean-Marc Valin
2004-01-06 2:08 ` Andrew Morton
2004-01-06 2:59 ` Valdis.Kletnieks
2004-01-06 6:33 ` Dax Kelson
2004-01-06 8:23 ` Jean-Marc Valin
2004-01-06 13:31 ` Valdis.Kletnieks
2004-03-29 15:46 ` Jean-Marc Valin
2004-03-29 15:46 ` Dax Kelson
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=1080617358.980.30.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=Administrator@smtp.paston.co.uk \
--cc=Jean-Marc.Valin@USherbrooke.ca \
--cc=akpm@osdl.org \
--cc=dax@gurulabs.com \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@intel.com \
/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