From: Lucas Stach <l.stach@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] doc: usb: add missing new line in codeblock
Date: Mon, 8 Dec 2014 15:45:23 +0100 [thread overview]
Message-ID: <1418049923-6176-1-git-send-email-l.stach@pengutronix.de> (raw)
Fixes an error during doc generation that leads to the
code block being missing in the resulting docs.
Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
---
Documentation/user/usb.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/user/usb.rst b/Documentation/user/usb.rst
index 88be62053629..0ff982bac462 100644
--- a/Documentation/user/usb.rst
+++ b/Documentation/user/usb.rst
@@ -155,6 +155,7 @@ value ``otg``. setting this to ``host`` or ``device`` puts the device in the cor
mode. Once a specific mode has been selected it can't be changed later anymore.
.. code-block:: sh
+
barebox:/ devinfo otg0
Parameters:
mode: otg ("otg", "host", "peripheral")
--
2.1.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-12-08 14:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 14:45 Lucas Stach [this message]
2014-12-09 9:00 ` Sascha Hauer
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=1418049923-6176-1-git-send-email-l.stach@pengutronix.de \
--to=l.stach@pengutronix.de \
--cc=barebox@lists.infradead.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