From: Richard Weinberger <richard@sigma-star.at>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Tom Rini <trini@konsulko.com>,
Richard Weinberger <richard@nod.at>,
upstream+uboot@sigma-star.at,
Francis Laniel <francis.laniel@amarulasolutions.com>,
Guillaume La Roque <glaroque@baylibre.com>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Christian Taedcke <christian.taedcke@weidmueller.com>
Subject: Re: [PATCH 1/3] test_fs: Allow running unprivileged
Date: Sun, 18 Aug 2024 22:06:05 +0200 [thread overview]
Message-ID: <2685504.bgRvk7e4E5@somecomputer> (raw)
In-Reply-To: <CAFLszThXOBKECTPy9nCLR5VYHVz6iauOVFYK9ZCai5CJZa2U3g@mail.gmail.com>
Simon,
Am Sonntag, 18. August 2024, 17:47:01 CEST schrieb Simon Glass:
> In that file, this is the line that builds the tools:
>
> ./tools/buildman/buildman -T0 -o ${UBOOT_TRAVIS_BUILD_DIR}
> -w --board tools-only
>
> and this adds the built scripts/dtc to the path, but you could just as
> easily add tools/
>
> export PATH=${UBOOT_TRAVIS_BUILD_DIR}/scripts/dtc:${PATH}
Sounds good. I guess this needs to go into master first before it shows
an effect on my branch?
Thanks,
//richard
--
sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT
UID/VAT Nr: ATU 66964118 | FN: 374287y
next prev parent reply other threads:[~2024-08-18 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 9:33 [PATCH 1/3] test_fs: Allow running unprivileged Richard Weinberger
2024-08-02 9:33 ` [PATCH 2/3] test_fs: Rename mount dir to scratch Richard Weinberger
2024-08-06 15:32 ` Mattijs Korpershoek
2024-08-06 16:42 ` Richard Weinberger
2024-08-02 9:33 ` [PATCH 3/3] test_ut: Allow running unprivileged Richard Weinberger
2024-08-06 15:29 ` [PATCH 1/3] test_fs: " Mattijs Korpershoek
2024-08-15 22:14 ` Tom Rini
2024-08-18 9:11 ` Richard Weinberger
2024-08-18 15:25 ` Simon Glass
2024-08-18 15:37 ` Richard Weinberger
2024-08-18 15:47 ` Simon Glass
2024-08-18 20:06 ` Richard Weinberger [this message]
2024-08-19 17:11 ` Tom Rini
2024-09-17 17:24 ` 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=2685504.bgRvk7e4E5@somecomputer \
--to=richard@sigma-star.at \
--cc=christian.taedcke@weidmueller.com \
--cc=francis.laniel@amarulasolutions.com \
--cc=glaroque@baylibre.com \
--cc=mkorpershoek@baylibre.com \
--cc=richard@nod.at \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=upstream+uboot@sigma-star.at \
/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