From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Clemens <john@deater.net>
Cc: cpufreq@ZenII.linux.org.uk
Subject: Re: [PATCH] pmac_cpufreq scaling_available_frequencies support..
Date: Mon, 07 Feb 2005 09:17:19 +1100 [thread overview]
Message-ID: <1107728239.30303.63.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.61.0502060129030.15763@pianoman.cluster.toy>
On Sun, 2005-02-06 at 01:37 -0500, John Clemens wrote:
> Hi, just a ping about this patch I sent back in ... err.. 2.6.8 days.
> I've updated it to 2.6.10 and wonder if there's any interest in it at all.
> (I certainly use it all the time, but hey..). The define cleanups may be
> unnecessary and can easily be dropped....looking at them now I'm not sure
> why i made them, actually. If there's interest I'll update to bk and drop
> the define stuff. If not, well, it's archived in the list if anyone wants
> it in the future.
That's fine, I've been away for a while and kept busy with other things
and forgot about those. Just ping me regulary.
At the moment, I'm fighting a more important problem with cpufreq
related to the CPU caches which can cause some machines to corrupt
memory.
Ben.
prev parent reply other threads:[~2005-02-06 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 6:37 [PATCH] pmac_cpufreq scaling_available_frequencies support John Clemens
2005-02-06 22:17 ` 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=1107728239.30303.63.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cpufreq@ZenII.linux.org.uk \
--cc=john@deater.net \
/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