From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Cc: "debian-powerpc@lists.debian.org" <debian-powerpc@lists.debian.org>
Subject: [PATCH] sleep & cpufreq problems
Date: Tue, 29 Mar 2005 13:28:54 +1000 [thread overview]
Message-ID: <1112066934.6809.4.camel@gaston> (raw)
Hi !
Here are a couple of patches against current linus bk (one was already
posted to this list) that should fix a number issues related to sleep
and wakeup, especially in conjunction with cpufreq transitions.
Please test and let me know if it fixes a problem you had, it adds a new
problem, or it has no effect, stuff still doesn't work (if it used to
work and still work, no need to bug me).
Thanks !
Patches are at:
http://gate.crashing.org/~benh/ppc32-pmac-sleep-fix.diff
http://gate.crashing.org/~benh/ppc32-cpufreq-gpio-off.diff
Thanks,
Ben.
next reply other threads:[~2005-03-29 3:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 3:28 Benjamin Herrenschmidt [this message]
2005-03-29 4:48 ` [PATCH] sleep & cpufreq problems Benjamin Herrenschmidt
2005-03-29 21:03 ` David Woodhouse
2005-03-29 16:34 ` Sebastien NOEL
2005-03-30 22:32 ` Benjamin Herrenschmidt
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=1112066934.6809.4.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@ozlabs.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