From: Dave Jones <davej@redhat.com>
To: cpufreq@lists.linux.org.uk
Subject: Re: [git pull] cpufreq governor updates for 2.6.17
Date: Mon, 27 Mar 2006 14:53:10 -0500 [thread overview]
Message-ID: <20060327195310.GA647@redhat.com> (raw)
In-Reply-To: <20060326095338.GA17358@dominikbrodowski.de>
On Sun, Mar 26, 2006 at 11:53:39AM +0200, Dominik Brodowski wrote:
> Hi Dave,
>
> Please pull from
> git://git.kernel.org/pub/scm/linux/kernel/git/brodo/cpufreq-2.6.git/
> for a few cpufreq updates for 2.6.17. The diffstat and list of changes
> follows, the patches will be sent out as individual mails as replies to this
> message.
I'm not entirely sure what happened here.
I git pull'd from this, and ended up with a 59,886 line delta against Linus' tree.
As you sent the diffs too, I'll just apply-mbox them.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-27 19:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 9:53 [git pull] cpufreq governor updates for 2.6.17 Dominik Brodowski
2006-03-26 9:54 ` [PATCH 001/007] cpufreq_conservative: aligning of codebase with ondemand Dominik Brodowski
2006-03-26 9:55 ` [PATCH 002/007] cpufreq_conservative: alter default responsiveness Dominik Brodowski
2006-03-26 9:55 ` [PATCH 003/007] cpufreq_conservative: make for_each_cpu() safe Dominik Brodowski
2006-03-26 9:56 ` [PATCH 004/007] cpufreq_conservative: alternative initialise approach Dominik Brodowski
2006-03-26 9:57 ` [PATCH 005/007] cpufreq_ondemand: Warn if it cannot run due to too long transition latency Dominik Brodowski
2006-03-26 9:57 ` [PATCH 006/007] cpufreq_ondemand: keep ignore_nice_load value when it is reselected Dominik Brodowski
2006-03-26 9:57 ` [PATCH 007/007] cpufreq_ondemand: add range check Dominik Brodowski
2006-03-27 19:53 ` Dave Jones [this message]
2006-03-27 19:58 ` [git pull] cpufreq governor updates for 2.6.17 Dave Jones
2006-03-27 21:06 ` Dominik Brodowski
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=20060327195310.GA647@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
/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