public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH edk2-platforms 1/4] Readme.md: wrap long line
Date: Wed, 15 Jul 2020 13:20:24 +0100	[thread overview]
Message-ID: <20200715122027.970-2-leif@nuviainc.com> (raw)
In-Reply-To: <20200715122027.970-1-leif@nuviainc.com>

The line describing how to set cross compiler prefix was way too long,
wrap it to match the rest of the file.

Signed-off-by: Leif Lindholm <leif@nuviainc.com>
---
 Readme.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Readme.md b/Readme.md
index ea9492240adb..c5df5a15f53d 100644
--- a/Readme.md
+++ b/Readme.md
@@ -159,7 +159,8 @@ build command which toolchain to use. We do this by setting the environment
 variable `{TOOL_CHAIN_TAG}_{TARGET_ARCH}_PREFIX` - in the case above,
 **GCC5_AARCH64_PREFIX**.
 
-So, referring to the cross compiler toolchain table above, we should prepend the `build` command line with `GCC5_AARCH64_PREFIX=aarch64-linux-gnu-`.
+So, referring to the cross compiler toolchain table above, we should prepend the
+`build` command line with `GCC5_AARCH64_PREFIX=aarch64-linux-gnu-`.
 
 ## Using uefi-tools helper scripts
 uefi-tools is a completely unofficial set of helper-scripts developed by Linaro.
-- 
2.20.1


  reply	other threads:[~2020-07-15 12:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15 12:20 [PATCH edk2-platforms 0/4] Readme.md: various build example updates Leif Lindholm
2020-07-15 12:20 ` Leif Lindholm [this message]
2020-07-15 12:20 ` [PATCH edk2-platforms 2/4] Readme.md: update build parallellism information Leif Lindholm
2020-07-21  3:58   ` [edk2-devel] " Bob Feng
2020-07-15 12:20 ` [PATCH edk2-platforms 3/4] Readme.md: update ARM/AARCH64 cross-toolchain info Leif Lindholm
2020-07-15 12:20 ` [PATCH edk2-platforms 4/4] Readme.md: add example command line to cross compiling section Leif Lindholm

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-list 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=20200715122027.970-2-leif@nuviainc.com \
    --to=devel@edk2.groups.io \
    /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