From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: cpuidle single/global and last_state fixes
Date: Fri, 11 Nov 2011 07:51:30 +0000 [thread overview]
Message-ID: <20111111075130.GI29807@linux-sh.org> (raw)
In-Reply-To: <20111111050130.9104.12599.sendpatchset@w520>
On Fri, Nov 11, 2011 at 02:01:30PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
>
> The following commits break cpuidle on SH-Mobile ARM:
>
> 46bcfad cpuidle: Single/Global registration of idle states
> e978aa7 cpuidle: Move dev->last_residency update to driver enter routine; remove dev->last_state
>
> This patch remedies these issues by up-porting the SH-Mobile
> code to fit with the above introduced framework changes.
>
> It is worth noting that the new code becomes significantly cleaner,
> so these framework changes are very welcome. At the same time this
> breakage could probably have been avoided by grepping for "last_state"
> and "cpuidle_register_driver".
>
> Signed-off-by: Magnus Damm <damm@opensource.se>
Applied, thanks.
prev parent reply other threads:[~2011-11-11 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 5:01 [PATCH] ARM: mach-shmobile: cpuidle single/global and last_state fixes Magnus Damm
2011-11-11 7:51 ` Paul Mundt [this message]
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=20111111075130.GI29807@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).