From: Jorge Marques <jorge.marques@analog.com>
To: "Nuno Sá" <nuno.sa@analog.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>
Cc: <linux-iio@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Jorge Marques <jorge.marques@analog.com>
Subject: [PATCH] docs: iio: ad3552r: Fix malformed code-block directive
Date: Mon, 18 Aug 2025 16:44:23 +0200 [thread overview]
Message-ID: <20250818-docs-ad3552r-code-block-fix-v1-1-4430cbc26676@analog.com> (raw)
Missing required double dot and line break.
Signed-off-by: Jorge Marques <jorge.marques@analog.com>
---
To resolve the code-block directive syntax not being parsed.
---
Documentation/iio/ad3552r.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/iio/ad3552r.rst b/Documentation/iio/ad3552r.rst
index f5d59e4e86c7ec8338f3f4e82d7a07587e3d8404..4274e35f503d9f7d8a5427a72d761d6549f4c683 100644
--- a/Documentation/iio/ad3552r.rst
+++ b/Documentation/iio/ad3552r.rst
@@ -64,7 +64,8 @@ specific debugfs path ``/sys/kernel/debug/iio/iio:deviceX``.
Usage examples
--------------
-. code-block:: bash
+.. code-block:: bash
+
root:/sys/bus/iio/devices/iio:device0# cat data_source
normal
root:/sys/bus/iio/devices/iio:device0# echo -n ramp-16bit > data_source
---
base-commit: 35e3d0cd8e89d811b915593cbd8d9891d21d4a1a
change-id: 20250818-docs-ad3552r-code-block-fix-6f680d124e5c
Best regards,
--
Jorge Marques <jorge.marques@analog.com>
next reply other threads:[~2025-08-18 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 14:44 Jorge Marques [this message]
2025-08-18 15:16 ` [PATCH] docs: iio: ad3552r: Fix malformed code-block directive David Lechner
2025-08-18 18:31 ` Jonathan Cameron
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=20250818-docs-ad3552r-code-block-fix-v1-1-4430cbc26676@analog.com \
--to=jorge.marques@analog.com \
--cc=andy@kernel.org \
--cc=corbet@lwn.net \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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).