From: Randy Dunlap <rdunlap@infradead.org>
To: Linux PM list <linux-pm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: [PATCH -next] Documentation/power: fix pm_qos_interface.rst format warning
Date: Sun, 16 Feb 2020 20:54:21 -0800 [thread overview]
Message-ID: <561e2780-111a-1939-43fb-ae32d7abce8d@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix Sphinx warnings by indenting the bullet list (and making it
unnumbered).
Documentation/power/pm_qos_interface.rst:12: WARNING: Unexpected indentation.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
---
Documentation/power/pm_qos_interface.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20200217.orig/Documentation/power/pm_qos_interface.rst
+++ linux-next-20200217/Documentation/power/pm_qos_interface.rst
@@ -7,8 +7,8 @@ performance expectations by drivers, sub
one of the parameters.
Two different PM QoS frameworks are available:
-1. CPU latency QoS.
-2. The per-device PM QoS framework provides the API to manage the
+ * CPU latency QoS.
+ * The per-device PM QoS framework provides the API to manage the
per-device latency constraints and PM QoS flags.
The latency unit used in the PM QoS framework is the microsecond (usec).
next reply other threads:[~2020-02-17 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 4:54 Randy Dunlap [this message]
2020-02-20 10:55 ` [PATCH -next] Documentation/power: fix pm_qos_interface.rst format warning Rafael J. Wysocki
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=561e2780-111a-1939-43fb-ae32d7abce8d@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).