From: Dave Jones <davej@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: cpufreq <cpufreq@www.linux.org.uk>, linux@markus-schaub.de
Subject: Re: [Bug 8671] CPU frequency always on highest frequency after wakeup from suspend to disk
Date: Tue, 26 Jun 2007 16:31:21 -0400 [thread overview]
Message-ID: <20070626203121.GC14751@redhat.com> (raw)
In-Reply-To: <1182866228.4249.102.camel@queen.suse.de>
On Tue, Jun 26, 2007 at 03:57:08PM +0200, Thomas Renninger wrote:
> On Tue, 2007-06-26 at 06:33 -0700, bugme-daemon@bugzilla.kernel.org
> wrote:
> > http://bugzilla.kernel.org/show_bug.cgi?id=8671
>
> > ------- Comment #10 from linux@markus-schaub.de 2007-06-26 06:37 -------
> > Yepp, the patch from Thomas works.
>
> Dave, is this acceptable?
> If yes, I expect you are going to pick it for the next kernel iteration
> and people still need to workaround this one in userspace or need to
> pick up the patch separately?
Yeah, looks like the easiest way to solve that.
Can you mail me a copy off-list, and I'll get to it
as soon as I get back from OLS ?
Thanks,
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-06-26 20:31 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 11:57 [Bug 8671] New: CPU frequency always on highest frequency after wakeup from suspend to disk bugme-daemon
2007-06-25 13:34 ` [Bug 8671] " bugme-daemon
[not found] ` <1182780094.22063.30.camel@queen.suse.de>
2007-06-25 14:11 ` Mattia Dongili
[not found] ` <1182784351.4249.3.camel@queen.suse.de>
[not found] ` <20070625153452.GC13308@inferi.kami.home>
[not found] ` <1182798023.4249.18.camel@queen.suse.de>
2007-06-26 6:22 ` [PATCH 2.6.22-rc6?] keep policy->user_policy in sync and use CPU0 policy as a template for other CPUs Mattia Dongili
2007-06-26 10:37 ` Thomas Renninger
2007-06-26 12:09 ` Mattia Dongili
2007-06-25 14:33 ` [Bug 8671] CPU frequency always on highest frequency after wakeup from suspend to disk bugme-daemon
2007-06-25 15:12 ` bugme-daemon
2007-06-25 16:18 ` bugme-daemon
2007-06-25 16:48 ` bugme-daemon
2007-06-25 16:55 ` bugme-daemon
2007-06-26 6:24 ` bugme-daemon
2007-06-26 6:24 ` bugme-daemon
2007-06-26 11:35 ` bugme-daemon
2007-06-26 12:58 ` bugme-daemon
2007-06-26 13:33 ` bugme-daemon
2007-06-26 13:57 ` Thomas Renninger
2007-06-26 20:31 ` Dave Jones [this message]
2007-06-27 9:28 ` Thomas Renninger
2007-06-28 4:16 ` Mattia Dongili
2007-06-26 14:12 ` bugme-daemon
2007-06-30 23:53 ` bugme-daemon
2007-07-01 0:00 ` bugme-daemon
2007-07-01 0:00 ` bugme-daemon
2007-08-08 16:57 ` bugme-daemon
2007-08-09 4:35 ` bugme-daemon
2007-08-09 14:07 ` bugme-daemon
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=20070626203121.GC14751@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=linux@markus-schaub.de \
--cc=trenn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.