From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH v3 4/6] buildman: Always use the full path in CROSS_COMPILE
Date: Mon, 24 Jun 2024 09:49:10 -0600 [thread overview]
Message-ID: <20240624154910.GC38804@bill-the-cat> (raw)
In-Reply-To: <20240623175622.1468600-5-sjg@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 562 bytes --]
On Sun, Jun 23, 2024 at 11:56:20AM -0600, Simon Glass wrote:
> The feature to set the toolchain path does not seem to be needed. It
> causes problems with venv (see [1]). Let's remove it.
>
> Add some tests while we are here.
>
> It does not look like any docs changes are needed for this.
>
> [1] https://patchwork.ozlabs.org/project/uboot/patch/20240621131423.2363294-6-sjg@chromium.org/
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Suggested-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-06-24 15:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 17:56 [PATCH v3 0/6] Add Binman code-coverage test to CI Simon Glass
2024-06-23 17:56 ` [PATCH v3 1/6] buildman: Add python3-coverage Simon Glass
2024-07-15 13:31 ` Simon Glass
2024-06-23 17:56 ` [PATCH v3 2/6] buildman: Add python3-pycryptodome Simon Glass
2024-07-15 13:31 ` Simon Glass
2024-06-23 17:56 ` [PATCH v3 3/6] buildman: Fix a few typos in toolchain code Simon Glass
2024-07-15 13:31 ` Simon Glass
2024-06-23 17:56 ` [PATCH v3 4/6] buildman: Always use the full path in CROSS_COMPILE Simon Glass
2024-06-24 15:49 ` Tom Rini [this message]
2024-06-25 0:06 ` Andrejs Cainikovs
2024-06-25 12:38 ` Simon Glass
2024-06-25 15:16 ` Andrejs Cainikovs
2024-06-26 8:00 ` Simon Glass
2024-06-26 8:43 ` Andrejs Cainikovs
2024-07-15 13:31 ` Simon Glass
2024-06-23 17:56 ` [PATCH v3 5/6] u_boot_pylib: Use correct coverage tool within venv Simon Glass
2024-07-15 13:31 ` Simon Glass
2024-06-23 17:56 ` [PATCH v3 6/6] CI: Run code-coverage test for Binman Simon Glass
2024-06-24 15:49 ` Tom Rini
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=20240624154910.GC38804@bill-the-cat \
--to=trini@konsulko.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=quentin.schulz@cherry.de \
--cc=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.