From: Stephen Kitt <steve@sk2.org>
To: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Jonathan Corbet <corbet@lwn.net>,
"Daniel W . S . Almeida" <dwlsalmeida@gmail.com>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Stephen Kitt <steve@sk2.org>
Subject: [PATCH] docs: driver-api/gpio/driver.rst: fix code blocks
Date: Thu, 12 Mar 2020 19:06:51 +0100 [thread overview]
Message-ID: <20200312180650.1365059-1-steve@sk2.org> (raw)
Two code blocks have duplicate declarations (:: and explicit
.. code-block), this fixes them, addressing these warnings:
Documentation/driver-api/gpio/driver.rst:425: WARNING: Unexpected indentation.
Documentation/driver-api/gpio/driver.rst:423: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:427: WARNING: Block quote ends without a blank line; unexpected unindent.
Documentation/driver-api/gpio/driver.rst:429: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:429: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:429: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:433: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:446: WARNING: Unexpected indentation.
Documentation/driver-api/gpio/driver.rst:440: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:440: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:447: WARNING: Block quote ends without a blank line; unexpected unindent.
Documentation/driver-api/gpio/driver.rst:449: WARNING: Definition list ends without a blank line; unexpected unindent.
Documentation/driver-api/gpio/driver.rst:462: WARNING: Unexpected indentation.
Documentation/driver-api/gpio/driver.rst:460: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:462: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:465: WARNING: Block quote ends without a blank line; unexpected unindent.
Documentation/driver-api/gpio/driver.rst:467: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:467: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:467: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:471: WARNING: Inline emphasis start-string without end-string.
Documentation/driver-api/gpio/driver.rst:478: WARNING: Inline emphasis start-string without end-string.
Fixes: 4e29b70d5437 ("Documentation: gpio: driver.rst: Fix warnings")
Signed-off-by: Stephen Kitt <steve@sk2.org>
---
Documentation/driver-api/gpio/driver.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/driver-api/gpio/driver.rst b/Documentation/driver-api/gpio/driver.rst
index 871922529332..9809f593c0ab 100644
--- a/Documentation/driver-api/gpio/driver.rst
+++ b/Documentation/driver-api/gpio/driver.rst
@@ -416,7 +416,7 @@ The preferred way to set up the helpers is to fill in the
struct gpio_irq_chip inside struct gpio_chip before adding the gpio_chip.
If you do this, the additional irq_chip will be set up by gpiolib at the
same time as setting up the rest of the GPIO functionality. The following
-is a typical example of a cascaded interrupt handler using gpio_irq_chip::
+is a typical example of a cascaded interrupt handler using gpio_irq_chip:
.. code-block:: c
@@ -453,7 +453,7 @@ is a typical example of a cascaded interrupt handler using gpio_irq_chip::
return devm_gpiochip_add_data(dev, &g->gc, g);
The helper support using hierarchical interrupt controllers as well.
-In this case the typical set-up will look like this::
+In this case the typical set-up will look like this:
.. code-block:: c
base-commit: 7d3d3254adaa61cba896f71497f56901deb618e5
--
2.24.1
next reply other threads:[~2020-03-12 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 18:06 Stephen Kitt [this message]
2020-03-12 18:34 ` [PATCH] docs: driver-api/gpio/driver.rst: fix code blocks Jonathan Neuschäfer
2020-03-12 19:02 ` Stephen Kitt
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=20200312180650.1365059-1-steve@sk2.org \
--to=steve@sk2.org \
--cc=bgolaszewski@baylibre.com \
--cc=corbet@lwn.net \
--cc=dwlsalmeida@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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).