mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH] fixup! Documentation: i.MX8M: add EVK barebox installation documentation
Date: Wed,  4 Jan 2023 08:20:40 +0100	[thread overview]
Message-ID: <20230104072040.3691226-1-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20230103215448.3655459-1-a.fatoum@pengutronix.de>

s/as an/at an/

Cc: Ulrich Ölmann <u.oelmann@pengutronix.de>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/boards/imx/nxp-imx8mn-evk.rst | 2 +-
 Documentation/boards/imx/nxp-imx8mp-evk.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/boards/imx/nxp-imx8mn-evk.rst b/Documentation/boards/imx/nxp-imx8mn-evk.rst
index 4c07b949dafb..978dfa2db66a 100644
--- a/Documentation/boards/imx/nxp-imx8mn-evk.rst
+++ b/Documentation/boards/imx/nxp-imx8mn-evk.rst
@@ -77,7 +77,7 @@ to the eMMC boot partition requires special handling:
   - The barebox image includes a 32KiB preamble that allows the image
     to be directly writable to the start of the SD-Card or eMMC user area.
     Unlike older i.MX8M, the i.MX8MN BootROM expects the bootloader to not
-    start as an offset when booting from eMMC boot partitions, thus the first
+    start at an offset when booting from eMMC boot partitions, thus the first
     32KiB must be stripped.
 
 The ``barebox_update`` command takes care of this and need just be
diff --git a/Documentation/boards/imx/nxp-imx8mp-evk.rst b/Documentation/boards/imx/nxp-imx8mp-evk.rst
index 60e9f9eaea5d..dde57a37faf9 100644
--- a/Documentation/boards/imx/nxp-imx8mp-evk.rst
+++ b/Documentation/boards/imx/nxp-imx8mp-evk.rst
@@ -85,7 +85,7 @@ to the eMMC boot partition requires special handling:
   - The barebox image includes a 32KiB preamble that allows the image
     to be directly writable to the start of the SD-Card or eMMC user area.
     Unlike older i.MX8M, the i.MX8MP BootROM expects the bootloader to not
-    start as an offset when booting from eMMC boot partitions, thus the first
+    start at an offset when booting from eMMC boot partitions, thus the first
     32KiB must be stripped.
 
 The ``barebox_update`` command takes care of this and need just be
-- 
2.30.2




  parent reply	other threads:[~2023-01-04  7:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 21:54 [PATCH] " Ahmad Fatoum
2023-01-04  7:00 ` Ulrich Ölmann
2023-01-04  7:20 ` Ahmad Fatoum [this message]
2023-01-04 10:50 ` 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=20230104072040.3691226-1-a.fatoum@pengutronix.de \
    --to=a.fatoum@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