From: Roland Hieber <rohieb@rohieb.name>
To: barebox@lists.infradead.org
Cc: Roland Hieber <rohieb@rohieb.name>
Subject: [PATCH 7/9] doc: boards: Phytec phyCORE-i.MX31: fix formatting, style
Date: Tue, 12 Jun 2018 00:02:33 +0200 [thread overview]
Message-ID: <20180611220235.15995-8-rohieb@rohieb.name> (raw)
In-Reply-To: <20180611220235.15995-1-rohieb@rohieb.name>
Signed-off-by: Roland Hieber <rohieb@rohieb.name>
---
Documentation/boards/imx/phytec-phycore-i.mx31.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/boards/imx/phytec-phycore-i.mx31.rst b/Documentation/boards/imx/phytec-phycore-i.mx31.rst
index 6c05bcdfdc..d9a981b998 100644
--- a/Documentation/boards/imx/phytec-phycore-i.mx31.rst
+++ b/Documentation/boards/imx/phytec-phycore-i.mx31.rst
@@ -23,8 +23,8 @@ Supported baseboards
Supported baseboards are:
* Silica / Phytec PCM-970 via phyMAP-i.MX31, PMA-001
-How to get barebox for 'Phytec's phyCORE-i.MX31'
-------------------------------------------------
+How to get barebox for Phytec's phyCORE-i.MX31
+----------------------------------------------
Using the default configuration::
@@ -34,8 +34,8 @@ Build the binary image::
make ARCH=arm CROSS_COMPILE=armv5compiler
-**NOTE:** replace ''armv5compiler'' with your ARM v5 cross compiler,
- e.g.: ''arm-1136jfs-linux-gnueabi-''
+.. note:: replace ``armv5compiler`` with your ARM v5 cross compiler prefix,
+ e.g.: ``arm-1136jfs-linux-gnueabi-``
The resulting binary image to be flashed will be ``barebox.bin``, whereas
the file named just ``barebox`` is an ELF executable for ARM.
--
2.17.1
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-06-11 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 22:02 [PATCH 0/9] small nit-picks for the i.MX boards documentation Roland Hieber
2018-06-11 22:02 ` [PATCH 1/9] doc: boards: imx: order table of contents alphabetically Roland Hieber
2018-06-11 22:02 ` [PATCH 2/9] doc: boards: Amazon Kindle 4/5: apply some more formatting Roland Hieber
2018-06-11 22:02 ` [PATCH 3/9] doc: boards: Amazon Kindle 3: apply " Roland Hieber
2018-06-11 22:02 ` [PATCH 4/9] doc: boards: element14 WaRP7: fix header level and nested list Roland Hieber
2018-06-11 22:02 ` [PATCH 5/9] doc: boards: Garz+Fricke Vincell: fix header level, capitalization and punctuation Roland Hieber
2018-06-11 22:02 ` [PATCH 6/9] doc: boards: Ka-Ro TX6: use official spelling of Ka-Ro Roland Hieber
2018-06-11 22:02 ` Roland Hieber [this message]
2018-06-11 22:02 ` [PATCH 8/9] doc: boards: Synertronixx SCB9328: use official uppercase spelling Roland Hieber
2018-06-11 22:02 ` [PATCH 9/9] doc: boards: Wandboard: fix formatting and punctuation Roland Hieber
2018-06-13 7:16 ` [PATCH 0/9] small nit-picks for the i.MX boards documentation 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=20180611220235.15995-8-rohieb@rohieb.name \
--to=rohieb@rohieb.name \
--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