linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Sergei Shtylyov
	<sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	balbi-l0cyMroinI0@public.gmane.org,
	linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 3/4] usb: musb: omap2430: use SIMPLE_DEV_PM_OPS
Date: Sun, 22 Sep 2013 17:02:03 +0200	[thread overview]
Message-ID: <523F066B.1030304@gmail.com> (raw)
In-Reply-To: <523F05C4.50104-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>

On 22.09.2013 16:59, Sergei Shtylyov wrote:
> On 22-09-2013 18:43, Daniel Mack wrote:
> 
>> This makes omap2430_pm_ops const and will stub the struct out in case
>> CONFIG_PM_SLEEP is not set.
> 
>> Signed-off-by: Daniel Mack <zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> ---
>>   drivers/usb/musb/omap2430.c | 15 +++++----------
>>   1 file changed, 5 insertions(+), 10 deletions(-)
> 
>> diff --git a/drivers/usb/musb/omap2430.c b/drivers/usb/musb/omap2430.c
>> index 59d2245..be42460 100644
>> --- a/drivers/usb/musb/omap2430.c
>> +++ b/drivers/usb/musb/omap2430.c
>> @@ -659,17 +659,12 @@ static int omap2430_runtime_resume(struct device *dev)
>>
>>   	return 0;
>>   }
>> -
>> -static struct dev_pm_ops omap2430_pm_ops = {
>> -	.runtime_suspend = omap2430_runtime_suspend,
>> -	.runtime_resume = omap2430_runtime_resume,
>> -};
>> -
>> -#define DEV_PM_OPS	(&omap2430_pm_ops)
>> -#else
>> -#define DEV_PM_OPS	NULL
>>   #endif
>>
>> +static SIMPLE_DEV_PM_OPS(omap2430_pm_ops,
>> +			 omap2430_runtime_suspend,
>> +			 omap2430_runtime_resume);
> 
>     No, SIMPLE_DEV_PM_OPS() won't do here, it's runtime PM, didn't you see?

Eh, you're right, sorry. Whoever applies this series, just drop that one
patch. The rest of this series is not affected.

Sergei, thanks for the review again :)


Daniel

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2013-09-22 15:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-22 14:43 [PATCH v2 1/4] usb: musb: am35x: use SIMPLE_DEV_PM_OPS Daniel Mack
     [not found] ` <1379860999-7106-1-git-send-email-zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-22 14:43   ` [PATCH v2 2/4] usb: musb: blackfin: " Daniel Mack
2013-09-22 14:43   ` [PATCH v2 3/4] usb: musb: omap2430: " Daniel Mack
     [not found]     ` <1379860999-7106-3-git-send-email-zonque-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-22 14:59       ` Sergei Shtylyov
     [not found]         ` <523F05C4.50104-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2013-09-22 15:02           ` Daniel Mack [this message]
2013-09-22 14:43   ` [PATCH v2 4/4] usb: musb: ux500: " Daniel Mack

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=523F066B.1030304@gmail.com \
    --to=zonque-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=balbi-l0cyMroinI0@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sergei.shtylyov-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.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).