Messages in this thread Patch in this message | | | From | Jonathan Neuschäfer <> | Subject | [PATCH] Documentation: gpio: driver: Format code blocks properly | Date | Wed, 2 Oct 2019 16:41:41 +0200 |
| |
This fixes a lot of Sphinx warnings, and makes the code blocks look nice in HTML.
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> --- Documentation/driver-api/gpio/driver.rst | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/Documentation/driver-api/gpio/driver.rst b/Documentation/driver-api/gpio/driver.rst index 3fdb32422f8a..18dca55eddfd 100644 --- a/Documentation/driver-api/gpio/driver.rst +++ b/Documentation/driver-api/gpio/driver.rst @@ -415,6 +415,8 @@ 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:
+.. code-block:: c + /* Typical state container with dynamic irqchip */ struct my_gpio { struct gpio_chip gc; @@ -450,6 +452,8 @@ is a typical example of a cascaded interrupt handler using gpio_irq_chip: The helper support using hierarchical interrupt controllers as well. In this case the typical set-up will look like this:
+.. code-block:: c + /* Typical state container with dynamic irqchip */ struct my_gpio { struct gpio_chip gc; -- 2.20.1
| |