From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 1/2] shdmac: use SET_RUNTIME_PM_OPS()
Date: Wed, 11 Feb 2015 10:47:31 +0000 [thread overview]
Message-ID: <54DB3343.1030009@cogentembedded.com> (raw)
In-Reply-To: <9005734.b9UuUHqyUV@wasted.cogentembedded.com>
Hello.
On 2/11/2015 4:23 AM, Vinod Koul wrote:
>> Use SET_RUNTIME_PM_OPS() to initialize the runtime PM method pointers in the
>> 'struct dev_pm_ops'; since that macro doesn't do anything if CONFIG_PM is
>> not defined, we have to move #ifdef up to also cover the runtime PM methods
>> in order to avoid compilation warnings.
> Applied both, thanks.
Thanks to you! Will they get into 3.20?
> Btw shdmac is NOT a subsystem name!!
Sorry, I usually don't add the subsystem names, leaving that to the
maintainers who want (or don't want) to do it.
WBR, Sergei
next prev parent reply other threads:[~2015-02-11 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 21:09 [PATCH v2 1/2] shdmac: use SET_RUNTIME_PM_OPS() Sergei Shtylyov
2015-02-11 1:35 ` Vinod Koul
2015-02-11 10:47 ` Sergei Shtylyov [this message]
2015-02-13 8:44 ` Vinod Koul
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=54DB3343.1030009@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).