From: Pavel Machek <pavel@ucw.cz>
To: Vinod Koul <vinod.koul@intel.com>
Cc: linux-kernel@vger.kernel.org, subhransu.s.prusty@intel.com,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>,
Randy Dunlap <rdunlap@infradead.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-pm@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH 01/27] PM: Add helper pm_runtime_last_busy_and_autosuspend()
Date: Wed, 24 Sep 2014 19:54:10 +0200 [thread overview]
Message-ID: <20140924175410.GC1231@amd> (raw)
In-Reply-To: <1411575342-31048-2-git-send-email-vinod.koul@intel.com>
On Wed 2014-09-24 21:44:51, Vinod Koul wrote:
> From: Subhransu S. Prusty <subhransu.s.prusty@intel.com>
>
> pm_runtime_mark_last_busy and pm_runtime_put_autosuspend are used together
> in quite a lot of places. Add a helper for these.
> Also updated Documentation for this
With function name as long as the implementation... I'm not sure if
this is good helper :-).
Pavel
> +static inline int pm_runtime_last_busy_and_autosuspend(struct device *dev)
> +{
> + pm_runtime_mark_last_busy(dev);
> + return pm_runtime_put_autosuspend(dev);
> +}
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-09-24 17:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 16:14 [PATCH 00/27] add pm_runtime_last_busy_and_autosuspend() helper Vinod Koul
2014-09-24 16:14 ` [PATCH 01/27] PM: Add helper pm_runtime_last_busy_and_autosuspend() Vinod Koul
2014-09-24 17:54 ` Pavel Machek [this message]
2014-09-25 8:00 ` Vinod Koul
2014-09-25 8:13 ` Ulf Hansson
2014-09-24 16:15 ` [PATCH 20/27] pm2301-charger: use pm_runtime_last_busy_and_autosuspend helper Vinod Koul
2014-09-24 20:28 ` [PATCH 00/27] add pm_runtime_last_busy_and_autosuspend() helper Rafael J. Wysocki
2014-09-24 20:15 ` Felipe Balbi
2014-09-24 20:46 ` Rafael J. Wysocki
2014-09-24 20:32 ` Felipe Balbi
2014-09-25 7:57 ` Vinod Koul
2014-09-25 14:22 ` Felipe Balbi
2014-09-25 14:27 ` Wolfram Sang
2014-09-25 19:54 ` Rafael J. Wysocki
2014-09-28 15:37 ` Vinod Koul
2014-09-25 7:46 ` 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=20140924175410.GC1231@amd \
--to=pavel@ucw.cz \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
--cc=subhransu.s.prusty@intel.com \
--cc=ulf.hansson@linaro.org \
--cc=vinod.koul@intel.com \
/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).