From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Jones <davej@suse.de>
Cc: Dominik Brodowski <linux@brodo.de>,
anders@trudheim.com, cpufreq@www.linux.org.uk
Subject: Re: rebased cpufreq patch?
Date: 07 Jul 2003 20:38:32 +0200 [thread overview]
Message-ID: <1057603112.11708.82.camel@gaston> (raw)
In-Reply-To: <20030707193839.C9758@suse.de>
On Mon, 2003-07-07 at 19:38, Dave Jones wrote:
> I've no objection really, but it does mean that we would be introducing
> an already obsolete interface into mainline. (~Not htat that's really a
> problem, we did already for 2.5 anyway).
I'd like to see the core in asap, if possible for .22, and I don't
care that much about the interface right now...
The point is that a bunch of recent Apple laptops boot at low speed
by default, and the only way I provide to switch them to full speed
is via cpufreq... That's one of the few bits still preventing me
to fully merge my "powermac" kernels into mainline.
Ben.
prev parent reply other threads:[~2003-07-07 18:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-07 12:34 rebased cpufreq patch? Dominik Brodowski
2003-07-07 17:38 ` Dave Jones
2003-07-07 18:38 ` Benjamin Herrenschmidt [this message]
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=1057603112.11708.82.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=anders@trudheim.com \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@suse.de \
--cc=linux@brodo.de \
/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