From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Voluspa <lista1@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc6 missing commit(s) in cpufreq?
Date: Fri, 17 Jun 2005 20:35:49 +1000 [thread overview]
Message-ID: <20050617203549.4ecf5670.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20050617122155.0d8190c2.lista1@telia.com>
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]
On Fri, 17 Jun 2005 12:21:55 +0200 Voluspa <lista1@telia.com> wrote:
>
> commit 1206aaac285904e3e3995eecbf4129b6555a8973
> Author: Dave Jones <davej@redhat.com>
> Date: Tue May 31 19:03:48 2005 -0700
>
> [CPUFREQ] Allow ondemand stepping to be changed by user.
>
> And when I look at:
> http://www.kernel.org/git/?p=linux/kernel/git/davej/cpufreq.git;a=commit;h=1206aaac285904e3e3995eecbf4129b6555a8973
>
> There are changes in the diff like:
>
> --- drivers/cpufreq/cpufreq_ondemand.c
> +++ drivers/cpufreq/cpufreq_ondemand.c
> @@ -79,6 +79,7 @@ struct dbs_tuners {
> unsigned int up_threshold;
> unsigned int down_threshold;
> unsigned int ignore_nice;
> + unsigned int freq_step;
> };
>
> Problem is that neither a clean 2.6.11 patched with patch-2.6.12-rc6 nor
> a full linux-2.6.12-rc6.tar.bz (I just downloaded it) contain that
> commit.
>
> The first example from above looks like:
>
> struct dbs_tuners {
> unsigned int sampling_rate;
> unsigned int sampling_down_factor;
> unsigned int up_threshold;
> unsigned int ignore_nice;
> };
Commit c29f1403098135bdef75b190a5037db514701031 removes that element of
struct dbs_tuners again.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-17 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 10:21 Voluspa
2005-06-17 10:35 ` Stephen Rothwell [this message]
2005-06-17 10:48 ` Voluspa
2005-06-17 10:41 ` Eric Piel
2005-06-17 10:56 ` Voluspa
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=20050617203549.4ecf5670.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.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
all inboxes | Powered by JetHome®