From: Bruno Ducrot <ducrot@poupinou.org>
To: Eric Piel <Eric.Piel@tremplin-utc.net>
Cc: davej@redhat.com, cpufreq@zenii.linux.org.uk,
Jan De Luyck <lkml@kcore.org>,
linux-kernel@vger.kernel.org, linux@dominikbrodowski.net
Subject: Re: cpufreq on-demand governor up_treshold?
Date: Mon, 14 Mar 2005 12:19:50 +0100 [thread overview]
Message-ID: <20050314111950.GE2298@poupinou.org> (raw)
In-Reply-To: <42354400.7070500@tremplin-utc.net>
On Mon, Mar 14, 2005 at 08:57:52AM +0100, Eric Piel wrote:
> BTW, DaveJ, Dominik, I couldn't find them in the daily-snapshot
> available at codemonkey.org.uk. Should I worry, or is it just due to
> some latency between your private trees and the public one?
>
This happens those days only when I upgrade the LINUX_2_4 branch
(and only because its easier for me to diff between HEAD and LINUX_2_4).
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2005-03-14 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 7:29 cpufreq on-demand governor up_treshold? Jan De Luyck
2005-03-14 7:57 ` Eric Piel
2005-03-14 11:19 ` Bruno Ducrot [this message]
2005-03-14 12:40 ` Jan De Luyck
2005-03-14 22:39 ` Dominik Brodowski
2005-05-11 1:33 ` Dave Jones
2005-05-11 2:34 ` Dave Jones
2005-05-11 12:19 ` Eric Piel
2005-05-11 12:23 ` [PATCH] [1/3] ondemand governor clean-up Eric Piel
2005-05-11 12:27 ` [PATCH][2/3] ondemand governor store the idle ticks for all cpus Eric Piel
2005-05-11 12:31 ` [PATCH][3/3] ondemand governor automatic downscaling Eric Piel
2005-05-12 23:16 ` cpufreq on-demand governor up_treshold? Eric Piel
2005-05-17 0:15 ` [PATCH] ondemand,conservative minor bug-fix and cleanup Venkatesh Pallipadi
-- strict thread matches above, loose matches on Subject: below --
2005-05-11 16:00 cpufreq on-demand governor up_treshold? Pallipadi, Venkatesh
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=20050314111950.GE2298@poupinou.org \
--to=ducrot@poupinou.org \
--cc=Eric.Piel@tremplin-utc.net \
--cc=cpufreq@zenii.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=lkml@kcore.org \
/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