From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk, dwmw2@redhat.com
Subject: Re: cpufreq suspend patch.
Date: Tue, 09 Aug 2005 10:32:39 +0200 [thread overview]
Message-ID: <1123576360.30257.153.camel@gaston> (raw)
In-Reply-To: <20050808224401.GA3277@redhat.com>
On Mon, 2005-08-08 at 18:44 -0400, Dave Jones wrote:
> Ben,
> Dave Woodhouse added this to the Fedora kernel a while back
> with the helpful comment "Fix ppc32 sleep/cpufreq harder"
> I believe this came from you originally.
>
> Can you comment on this ?
>
> It seems to make sense to me, but if you have a newer patch
> I'm all ears..
Can you compare with what's currently upstream ? (I'm still travelling
around so it's more difficult for me).
Ben.
next prev parent reply other threads:[~2005-08-09 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 22:44 cpufreq suspend patch Dave Jones
2005-08-09 8:32 ` Benjamin Herrenschmidt [this message]
2005-08-09 8:53 ` David Woodhouse
2005-08-09 8:54 ` Benjamin Herrenschmidt
2005-08-09 16:25 ` Dave Jones
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=1123576360.30257.153.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=dwmw2@redhat.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