From: Dave Jones <davej@redhat.com>
To: Stelian Pop <stelian@popies.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
davej@codemonkey.org.uk, cpufreq@www.linux.org.uk
Subject: Re: [PATCH 2.6] cpufreq longrun driver fix
Date: Mon, 5 Apr 2004 18:59:40 +0100 [thread overview]
Message-ID: <20040405175940.GO5688@redhat.com> (raw)
In-Reply-To: <20040405173835.GA7328@dominikbrodowski.de>
> > The following patch does even more, it tries every value from 80%
> > to 10% in 10% steps, until it succeeds in lowering the performance.
> > I'm not sure this is the best way to do it but in any case,
> > it works for me (and should continue to work for everybody else).
>
> Patch looks good to me -- thanks, Stelian!
> Dave, could you merge it, please?
Yup, will be in cpufreq-bk soon, and the next -mm that
Andrew rolls up.
Dave
prev parent reply other threads:[~2004-04-05 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 15:50 [PATCH 2.6] cpufreq longrun driver fix Stelian Pop
2004-04-05 17:38 ` Dominik Brodowski
2004-04-05 17:59 ` 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=20040405175940.GO5688@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=stelian@popies.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