From: peter@bikeshed.quignogs.org.uk
To: linux-doc@vger.kernel.org
Cc: Peter Lister <peter@bikeshed.quignogs.org.uk>,
Jonathan Corbet <corbet@lwn.net>
Subject: [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c".
Date: Mon, 9 Mar 2020 00:04:21 +0000 [thread overview]
Message-ID: <20200309000421.9397-1-peter@bikeshed.quignogs.org.uk> (raw)
From: Peter Lister <peter@bikeshed.quignogs.org.uk>
This makes the documentation build a little happier and removes
"Unexpected indentation" warnings.
Signed-off-by: Peter Lister <peter@bikeshed.quignogs.org.uk>
---
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
--
2.24.1
next reply other threads:[~2020-03-09 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 0:04 peter [this message]
2020-03-09 8:02 ` [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c" Jonathan Neuschäfer
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=20200309000421.9397-1-peter@bikeshed.quignogs.org.uk \
--to=peter@bikeshed.quignogs.org.uk \
--cc=corbet@lwn.net \
--cc=linux-doc@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).