* [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c".
@ 2020-03-09 0:04 peter
2020-03-09 8:02 ` Jonathan Neuschäfer
0 siblings, 1 reply; 2+ messages in thread
From: peter @ 2020-03-09 0:04 UTC (permalink / raw)
To: linux-doc; +Cc: Peter Lister, Jonathan Corbet
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c".
2020-03-09 0:04 [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c" peter
@ 2020-03-09 8:02 ` Jonathan Neuschäfer
0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Neuschäfer @ 2020-03-09 8:02 UTC (permalink / raw)
To: peter; +Cc: linux-doc, Jonathan Corbet
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
Hello Peter,
On Mon, Mar 09, 2020 at 12:04:21AM +0000, peter@bikeshed.quignogs.org.uk wrote:
> -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:
Mauro has already fixed this in linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=c1c8b1ff0a1985d4992f49a5775bbcf6ee5ccfba
I'm sure there's still plenty of other stuff to fix, though!
Thanks,
Jonathan Neuschäfer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-03-09 8:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-09 0:04 [PATCH 1/1] Changed double colon to single colon at the ends of two paragraphs preceding ".. code-block:: c" peter
2020-03-09 8:02 ` Jonathan Neuschäfer
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.