All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: kernel: cpu: provide 'NULL' parameter for calling cpuidle_register().
Date: Wed, 31 Jul 2013 08:37:20 +0000	[thread overview]
Message-ID: <51F8CCC0.1090302@asianux.com> (raw)
In-Reply-To: <51F8BB73.2070603@asianux.com>

On 07/31/2013 03:35 PM, Daniel Lezcano wrote:
> On 07/31/2013 09:23 AM, Chen Gang wrote:
>> 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>
>> ---
> 
> Thanks for the patch.
> 
> I have the same fix in my tree sent by Geert Uytterhoeven
> 
>   -- Daniel
> 
> 

OK, thanks, and I will send another patches.

:-)

-- 
Chen Gang

  parent reply	other threads:[~2013-07-31  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  7:23 [PATCH] sh: kernel: cpu: provide 'NULL' parameter for calling cpuidle_register() Chen Gang
2013-07-31  7:35 ` Daniel Lezcano
2013-07-31  8:37 ` Chen Gang [this message]
2013-07-31  9:04   ` [PATCH] scripts/recordmcount.pl: remove "-m32" for sh architecture Chen Gang
2013-07-31  9:04     ` 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=51F8CCC0.1090302@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.