From: Ducrot Bruno <ducrot@poupinou.org>
To: "Yu, Luming" <luming.yu@intel.com>
Cc: acpi-devel@lists.sourceforge.net, cpufreq@www.linux.org.uk,
Nate Lawson <nate@root.org>
Subject: Re: [ACPI] [PATCH] acpi-cpufreq fixups
Date: Mon, 19 Jan 2004 15:17:03 +0100 [thread overview]
Message-ID: <20040119141703.GH25416@poupinou.org> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720CF4@PDSMSX403.ccr.corp.intel.com>
On Sun, Jan 18, 2004 at 03:41:32PM +0800, Yu, Luming wrote:
> > Just checked linus' bk tree. It's a 20031002. Well, I must admit
> > that I was thinking it was more recent than that.
> >
> You can find latest ACPI patch for 2.6 at
> http://www.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/release/
> 2.6.1/
>
Yes I know. It just that I expected that linus bk contained a more
recent ACPI version.
I just hope that the issue of getting the most recent, and stable,
version of ACPI in a stable kernel serie we got the last two years
do not happen anymore.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-19 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 7:41 [PATCH] acpi-cpufreq fixups Yu, Luming
2004-01-19 14:17 ` Ducrot Bruno [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 23:32 Dominik Brodowski
2004-01-16 14:01 ` [ACPI] " Ducrot Bruno
2004-01-16 17:35 ` Nate Lawson
2004-01-16 19:32 ` Ducrot Bruno
2004-01-16 21:02 ` Ducrot Bruno
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=20040119141703.GH25416@poupinou.org \
--to=ducrot@poupinou.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=cpufreq@www.linux.org.uk \
--cc=luming.yu@intel.com \
--cc=nate@root.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