From: Stefan Lengfeld <contact@stefanchrist.eu>
To: barebox@lists.infradead.org
Subject: [PATCH 3/5] docs: fix hiding of chapter from imx.rst
Date: Mon, 15 May 2017 19:14:20 +0200 [thread overview]
Message-ID: <20170515171422.1648-3-contact@stefanchrist.eu> (raw)
In-Reply-To: <20170515171422.1648-1-contact@stefanchrist.eu>
The files 'mxs.rst' and 'imx.rst' used the same chapter headline:
Freescale i.MXs
This confuses sphinx. It does not support having the same headline at
the same level twice and hides the other chapter. Just rename the
chapter heading to avoid that.
And rename the subchapter headline to 'MXS boards' for clarity.
Signed-off-by: Stefan Lengfeld <contact@stefanchrist.eu>
---
Documentation/boards/mxs.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/boards/mxs.rst b/Documentation/boards/mxs.rst
index ad10b87..82f2321 100644
--- a/Documentation/boards/mxs.rst
+++ b/Documentation/boards/mxs.rst
@@ -1,5 +1,5 @@
-Freescale i.MXs
-===============
+Freescale MXS
+=============
Freescale i.MXs or MXS are a SoC family which consists of the i.MX23
and the i.MX28. These are quite different from the regular i.MX SoCs
@@ -118,8 +118,8 @@ Booting second stage
The second stage images can be started with the barebox :ref:`command_bootm` command or
just jumped into using the :ref:`command_go` command.
-i.MXs boards
-------------
+MXS boards
+----------
Not all supported boards have a description here.
--
2.7.4
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2017-05-15 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 17:14 [PATCH 1/5] images: clean *.imx-sram-img files Stefan Lengfeld
2017-05-15 17:14 ` [PATCH 2/5] imx-usb-loader: add prefix '0x' for hex value Stefan Lengfeld
2017-05-15 17:14 ` Stefan Lengfeld [this message]
2017-05-15 17:14 ` [PATCH 4/5] docs: add file suffix rst for inclusion in sphinx documentation Stefan Lengfeld
2017-05-15 17:14 ` [PATCH 5/5] docs: render DIP switches as verbatim text Stefan Lengfeld
2017-05-17 6:52 ` [PATCH 1/5] images: clean *.imx-sram-img files 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=20170515171422.1648-3-contact@stefanchrist.eu \
--to=contact@stefanchrist.eu \
--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