From: Rusty Lynch <rusty@linux.co.intel.com>
To: jordan.breeding@attbi.com
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][TRIVIAL] ACPI_PROCESSOR depends on CPU_FREQ
Date: 06 Feb 2003 13:46:38 -0800 [thread overview]
Message-ID: <1044567999.3106.23.camel@vmhack> (raw)
In-Reply-To: <200302062142.h16LgaF20694@caduceus.jf.intel.com>
On Thu, 2003-02-06 at 13:46, jordan.breeding@attbi.com wrote:
> I think that this: http://linus.bkbits.net:8080/linux-
> 2.5/diffs/drivers/acpi/processor.c@1.32?nav=index.html|ChangeSet@-
> 1d|cset@1.967.1.1 might be the real fix you are looking for which was commited
> not long ago.
>
> Jordan
yep, the next changeset fixes this.
--rustyl
> > After pulling from Linus's tree my build broke while attempting to
> > compile drivers/acpi/processor.c because cpufreq_get_policy() and
> > cpufreq_set_policy() were not defined.
> >
> > Here is a quick Kconfig fix.
> >
> > --rustyl
next parent reply other threads:[~2003-02-06 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200302062142.h16LgaF20694@caduceus.jf.intel.com>
2003-02-06 21:46 ` Rusty Lynch [this message]
2003-02-06 21:28 [PATCH][TRIVIAL] ACPI_PROCESSOR depends on CPU_FREQ Rusty Lynch
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=1044567999.3106.23.camel@vmhack \
--to=rusty@linux.co.intel.com \
--cc=jordan.breeding@attbi.com \
--cc=linux-kernel@vger.kernel.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