From: Ducrot Bruno <ducrot@poupinou.org>
To: Nate Lawson <nate@root.org>
Cc: acpi-devel@lists.sourceforge.net, cpufreq@www.linux.org.uk
Subject: Re: [ACPI] [PATCH] acpi-cpufreq fixups
Date: Fri, 16 Jan 2004 22:02:09 +0100 [thread overview]
Message-ID: <20040116210209.GD14031@poupinou.org> (raw)
In-Reply-To: <20040116193207.GC14031@poupinou.org>
On Fri, Jan 16, 2004 at 08:32:07PM +0100, Ducrot Bruno wrote:
> On Fri, Jan 16, 2004 at 09:35:11AM -0800, Nate Lawson wrote:
> > On Fri, 16 Jan 2004, Ducrot Bruno wrote:
> > > > - fix OOPS when PST has core_frequency values of zero
> > >
> > > FYI: That one have been fixed by Nate Lawson by calling _INI for processors.
> > > I don't know if it is in acpi-ca yet. Of course, it is still safe
> > > to check if freq is 0.
> >
> > I was told it was in 20031203 but I don't know what Linux kernel version
> > has that dist. I haven't checked to be sure since my FreeBSD cpufreq code
> > is in a rough state right now. :)
>
> Well, my question was for ACPI-CA. Now, if that is put in Linux, or not,
> who cares ;)
>
Just checked linus' bk tree. It's a 20031002. Well, I must admit
that I was thinking it was more recent than that.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2004-01-16 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 23:32 [PATCH] acpi-cpufreq fixups 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 [this message]
2004-01-28 22:44 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 7:41 Yu, Luming
2004-01-19 14:17 ` [ACPI] " 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=20040116210209.GD14031@poupinou.org \
--to=ducrot@poupinou.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=cpufreq@www.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.