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 5/5] PM / Runtime: s/foo_process_requests/foo_process_next_request/
Date: Mon, 24 Mar 2014 21:31:31 +0100 [thread overview]
Message-ID: <1395693091-4813-5-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>
The example uses foo_process_next_request() everywhere else.
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
Documentation/power/runtime_pm.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/power/runtime_pm.txt b/Documentation/power/runtime_pm.txt
index 0c1c4124d23a..5f96daf8566a 100644
--- a/Documentation/power/runtime_pm.txt
+++ b/Documentation/power/runtime_pm.txt
@@ -870,7 +870,7 @@ Here is a schematic pseudo-code example:
foo->is_suspended = 0;
pm_runtime_mark_last_busy(&foo->dev);
if (foo->num_pending_requests > 0)
- foo_process_requests(foo);
+ foo_process_next_request(foo);
unlock(&foo->private_lock);
return 0;
}
--
1.7.9.5
next prev parent reply other threads:[~2014-03-24 20:33 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 ` [PATCH 2/5] PM / Runtime: Split line longer than 80 characters Geert Uytterhoeven
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 ` Geert Uytterhoeven [this message]
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-5-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®