linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: preeti <preeti@linux.vnet.ibm.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org
Subject: Re: linux-next: comment on pm tree commit
Date: Mon, 09 Jul 2012 14:59:07 +0530	[thread overview]
Message-ID: <4FFAA463.1020608@linux.vnet.ibm.com> (raw)
In-Reply-To: <201207091024.34585.rjw@sisk.pl>

On 07/09/2012 01:54 PM, Rafael J. Wysocki wrote:
> On Monday, July 09, 2012, Stephen Rothwell wrote:
>> Hi Rafael,
>>
>> I noticed commit b8eec56cd8e5 ("PM / cpuidle: System resume hang fix with
>> cpuidle") in the pm tree needs some work (I noticed it because it was
>> changed in a rebase ...).
>>
>> diff --git a/include/linux/cpuidle.h b/include/linux/cpuidle.h
>> index a6b3f2e..b90ccb2 100644
>> --- a/include/linux/cpuidle.h
>> +++ b/include/linux/cpuidle.h
>> @@ -146,6 +146,8 @@ extern void cpuidle_unregister_device(struct cpuidle_device *dev);
>>  
>>  extern void cpuidle_pause_and_lock(void);
>>  extern void cpuidle_resume_and_unlock(void);
>> +extern void cpuidle_pause(void);
>> +extern void cpuidle_resume(void);
>>  extern int cpuidle_enable_device(struct cpuidle_device *dev);
>>  extern void cpuidle_disable_device(struct cpuidle_device *dev);
>>  extern int cpuidle_wrap_enter(struct cpuidle_device *dev,
>> @@ -169,6 +171,8 @@ static inline void cpuidle_unregister_device(struct cpuidle_device *dev) { }
>>  
>>  static inline void cpuidle_pause_and_lock(void) { }
>>  static inline void cpuidle_resume_and_unlock(void) { }
>> +static inline cpuidle_pause(void) { }
>> +static inline cpuidle_resume(void) { }
>>
>> These need to be "static inline void".  I wonder what review and build
>> testing this went through (the above should produce warnings since they
>> are non void returning functions with no return statements).
> 
> Thanks for reporting this, I tried to fix a build issue in the original patch

I apologise for not having taken care of the above build scenario.

> hastily and failed miserably as you have noticed and then I build-tested a
> wrong tree.  Sorry.
> 
> It should be fixed now for real.
> 
> Thanks,
> Rafael
> 

Regards
Preeti


      reply	other threads:[~2012-07-09  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-08 23:40 linux-next: comment on pm tree commit Stephen Rothwell
2012-07-09  8:24 ` Rafael J. Wysocki
2012-07-09  9:29   ` preeti [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=4FFAA463.1020608@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=sfr@canb.auug.org.au \
    /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).