From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT-PULL] cpuidle fixes for 3.12
Date: Mon, 12 Aug 2013 11:41:29 +0200 [thread overview]
Message-ID: <5208ADC9.2050309@linaro.org> (raw)
The following changes since commit d4e4ab86bcba5a72779c43dc1459f71fea3d89c8:
Linux 3.11-rc5 (2013-08-11 18:04:20 -0700)
are available in the git repository at:
git://git.linaro.org/people/dlezcano/linux.git cpuidle/arm-next
for you to fetch changes up to 75d6137da195a1e059e1c814cb95635e168f85c0:
cpuidle: kirkwood: Make kirkwood_cpuidle_remove function static
(2013-08-12 11:28:50 +0200)
This series fixes some compilation issues:
* for SH, a parameter is missing for the cpuidle_register function
* for Calxeda, an _iomem annotation is missing for scu_base_addr variable
* for kirkwood, a static declaration is missing for the
kirkwood_cpuidle_remove function
Thanks
-- Daniel
----------------------------------------------------------------
Geert Uytterhoeven (1):
SH: cpuidle: Add missing parameter for cpuidle_register()
Jingoo Han (2):
cpuidle: calxeda: Add missing __iomem annotation
cpuidle: kirkwood: Make kirkwood_cpuidle_remove function static
arch/sh/kernel/cpu/shmobile/cpuidle.c | 4 +---
drivers/cpuidle/cpuidle-calxeda.c | 2 +-
drivers/cpuidle/cpuidle-kirkwood.c | 2 +-
3 files changed, 3 insertions(+), 5 deletions(-)
--
<http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next reply other threads:[~2013-08-12 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 9:41 Daniel Lezcano [this message]
2013-08-13 12:50 ` [GIT-PULL] cpuidle fixes for 3.12 Rafael J. Wysocki
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=5208ADC9.2050309@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).