From: Chen Gang <gang.chen@asianux.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH] sh: kernel: cpu: provide 'NULL' parameter for calling cpuidle_register().
Date: Wed, 31 Jul 2013 07:23:31 +0000 [thread overview]
Message-ID: <51F8BB73.2070603@asianux.com> (raw)
Need provide additional parameter for calling cpuidle_register() just
like some of another architectures have done, or can not pass compiling.
The related error (with kfr2r09_defconfig):
CC arch/sh/kernel/cpu/shmobile/cpuidle.o
arch/sh/kernel/cpu/shmobile/cpuidle.c: In function 'sh_mobile_setup_cpuidle':
arch/sh/kernel/cpu/shmobile/cpuidle.c:102:2: error: too few arguments to function 'cpuidle_register'
return cpuidle_register(&cpuidle_driver);
^
In file included from arch/sh/kernel/cpu/shmobile/cpuidle.c:16:0:
include/linux/cpuidle.h:130:12: note: declared here
extern int cpuidle_register(struct cpuidle_driver *drv,
^
Signed-off-by: Chen Gang <gang.chen@asianux.com>
---
arch/sh/kernel/cpu/shmobile/cpuidle.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/sh/kernel/cpu/shmobile/cpuidle.c b/arch/sh/kernel/cpu/shmobile/cpuidle.c
index d306225..5f88393 100644
--- a/arch/sh/kernel/cpu/shmobile/cpuidle.c
+++ b/arch/sh/kernel/cpu/shmobile/cpuidle.c
@@ -99,5 +99,5 @@ int __init sh_mobile_setup_cpuidle(void)
if (sh_mobile_sleep_supported & SUSP_SH_STANDBY)
cpuidle_driver.states[2].disabled = false;
- return cpuidle_register(&cpuidle_driver);
+ return cpuidle_register(&cpuidle_driver, NULL);
}
--
1.7.7.6
next reply other threads:[~2013-07-31 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 7:23 Chen Gang [this message]
2013-07-31 7:35 ` [PATCH] sh: kernel: cpu: provide 'NULL' parameter for calling cpuidle_register() Daniel Lezcano
2013-07-31 8:37 ` Chen Gang
2013-07-31 9:04 ` [PATCH] scripts/recordmcount.pl: remove "-m32" for sh architecture Chen Gang
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=51F8BB73.2070603@asianux.com \
--to=gang.chen@asianux.com \
--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