From: Dave Jones <davej@codemonkey.org.uk>
To: Dominik Brodowski <linux@brodo.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
cpufreq@www.linux.org.uk
Subject: Re: [PATCH 2.5.53] cpufreq: longhaul cleanup
Date: Mon, 30 Dec 2002 11:31:22 +0000 [thread overview]
Message-ID: <20021230113122.GC11633@suse.de> (raw)
In-Reply-To: <20021228231233.GB1310@brodo.de>
On Sun, Dec 29, 2002 at 12:12:33AM +0100, Dominik Brodowski wrote:
> Clean up searching code for best frequency and add some safety checks.
Looks ok from a cursory glance, but one thing I'm wondering is
if some of this code can be factored out a little. There seems to
be some duplication between the various CPU drivers.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-12-30 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 23:12 Dominik Brodowski
2002-12-30 11:31 ` Dave Jones [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=20021230113122.GC11633@suse.de \
--to=davej@codemonkey.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=torvalds@transmeta.com \
/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
Powered by JetHome