From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH 2/5] PM / Runtime: Split line longer than 80 characters
Date: Mon, 24 Mar 2014 21:31:28 +0100 [thread overview]
Message-ID: <1395693091-4813-2-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1395693091-4813-1-git-send-email-geert@linux-m68k.org>
From: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
Documentation/power/runtime_pm.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/power/runtime_pm.txt b/Documentation/power/runtime_pm.txt
index a5683a5662cb..f62deb66d5c1 100644
--- a/Documentation/power/runtime_pm.txt
+++ b/Documentation/power/runtime_pm.txt
@@ -401,11 +401,11 @@ drivers/base/power/runtime.c and include/linux/pm_runtime.h:
int pm_runtime_disable(struct device *dev);
- increment the device's 'power.disable_depth' field (if the value of that
field was previously zero, this prevents subsystem-level runtime PM
- callbacks from being run for the device), make sure that all of the pending
- runtime PM operations on the device are either completed or canceled;
- returns 1 if there was a resume request pending and it was necessary to
- execute the subsystem-level resume callback for the device to satisfy that
- request, otherwise 0 is returned
+ callbacks from being run for the device), make sure that all of the
+ pending runtime PM operations on the device are either completed or
+ canceled; returns 1 if there was a resume request pending and it was
+ necessary to execute the subsystem-level resume callback for the device
+ to satisfy that request, otherwise 0 is returned
int pm_runtime_barrier(struct device *dev);
- check if there's a resume request pending for the device and resume it
--
1.7.9.5
next prev parent reply other threads:[~2014-03-24 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 20:31 [PATCH 1/5] PM / Runtime: dev_pm_info.runtime_error is signed Geert Uytterhoeven
2014-03-24 20:31 ` Geert Uytterhoeven [this message]
2014-03-24 20:31 ` [PATCH 3/5] PM / Runtime: Correct documented return values for generic PM callbacks Geert Uytterhoeven
2014-03-24 20:31 ` [PATCH 4/5] PM / Runtime: GENERIC_SUBSYS_PM_OPS is gone Geert Uytterhoeven
2014-03-24 20:31 ` [PATCH 5/5] PM / Runtime: s/foo_process_requests/foo_process_next_request/ Geert Uytterhoeven
2014-03-26 16:55 ` [PATCH 1/5] PM / Runtime: dev_pm_info.runtime_error is signed Pavel Machek
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=1395693091-4813-2-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=ben.dooks@codethink.co.uk \
--cc=geert+renesas@glider.be \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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
all inboxes | Powered by JetHome®