U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Alexey Brodkin <abrodkin@synopsys.com>
Subject: [PATCH v2 3/6] buildman: Fix a few typos in toolchain code
Date: Fri, 21 Jun 2024 07:14:19 -0600	[thread overview]
Message-ID: <20240621131423.2363294-4-sjg@chromium.org> (raw)
In-Reply-To: <20240621131423.2363294-1-sjg@chromium.org>

Fix 'Thie' and capitalise 'unicode'.

Signed-off-by: Simon Glass <sjg@chromium.org>
Suggested-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
---

Changes in v2:
- Add new patch to fix a few typos in toolchain code

 tools/buildman/toolchain.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tools/buildman/toolchain.py b/tools/buildman/toolchain.py
index 79c7c11a110..324ad0e0821 100644
--- a/tools/buildman/toolchain.py
+++ b/tools/buildman/toolchain.py
@@ -175,9 +175,9 @@ class Toolchain:
     def MakeEnvironment(self, full_path):
         """Returns an environment for using the toolchain.
 
-        Thie takes the current environment and adds CROSS_COMPILE so that
+        This takes the current environment and adds CROSS_COMPILE so that
         the tool chain will operate correctly. This also disables localized
-        output and possibly unicode encoded output of all build tools by
+        output and possibly Unicode encoded output of all build tools by
         adding LC_ALL=C.
 
         Note that os.environb is used to obtain the environment, since in some
-- 
2.34.1


  parent reply	other threads:[~2024-06-21 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 13:14 [PATCH v2 0/6] Add Binman code-coverage test to CI Simon Glass
2024-06-21 13:14 ` [PATCH v2 1/6] buildman: Add python3-coverage Simon Glass
2024-06-21 15:22   ` Tom Rini
2024-06-21 13:14 ` [PATCH v2 2/6] buildman: Add python3-pycryptodome Simon Glass
2024-06-21 15:22   ` Tom Rini
2024-06-21 13:14 ` Simon Glass [this message]
2024-06-21 13:14 ` [PATCH v2 4/6] buildman: Support building within a Python venv Simon Glass
2024-06-21 13:14 ` [PATCH v2 5/6] u_boot_pylib: Use correct coverage tool within venv Simon Glass
2024-06-21 13:14 ` [PATCH v2 6/6] CI: Run code-coverage test for Binman Simon Glass

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=20240621131423.2363294-4-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=abrodkin@synopsys.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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