From: Bryan Brattlof via buildroot <buildroot@buildroot.org>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>,
Xuanhao Shi <X15000177@gmail.com>,
James Hilliard <james.hilliard1@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org, Romain Naour <romain.naour@smile.fr>,
Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [Buildroot] [PATCH v3 3/3] uboot/uboot: add new dependency to yamllint
Date: Fri, 12 Apr 2024 10:18:11 -0500 [thread overview]
Message-ID: <20240412151811.cty2f2uiwig2hiyd@bryanbrattlof.com> (raw)
In-Reply-To: <20240412055358.1354293-3-heiko.thiery@gmail.com>
On April 12, 2024 thus sayeth Heiko Thiery:
> Since U-Boot 2024.04 [1] binman also uses yamllint as dependency [2].
>
> [1] https://source.denx.de/u-boot/u-boot/-/commit/10fee88d42f
> [2] https://source.denx.de/u-boot/u-boot/-/blob/v2024.04/tools/buildman/requirements.txt?ref_type=tags#L3
>
> Signed-off-by: Heiko Thiery <heiko.thiery@gmail.com>
> ---
>
> v2: accidentally resend this series as v2
> (it's too early in the morning and no coffee yet)
>
> v3:
> - update URLs in the comment
>
> boot/uboot/uboot.mk | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Reviewed-by: Bryan Brattlof <bb@ti.com>
Thanks for this. I successfully built v2024.04 U-Boot for all of TI's K3
SoCs. One step closer for K3 :)
~Bryan
>
> diff --git a/boot/uboot/uboot.mk b/boot/uboot/uboot.mk
> index a894654698..0ee63cabdb 100644
> --- a/boot/uboot/uboot.mk
> +++ b/boot/uboot/uboot.mk
> @@ -276,10 +276,12 @@ UBOOT_DEPENDENCIES += host-vim
> endif
>
> ifeq ($(BR2_TARGET_UBOOT_USE_BINMAN),y)
> -# https://source.denx.de/u-boot/u-boot/-/blob/v2024.01/tools/buildman/requirements.txt
> +# https://source.denx.de/u-boot/u-boot/-/blob/v2024.04/tools/binman/binman.rst?plain=1#L377
> +# https://source.denx.de/u-boot/u-boot/-/blob/v2024.04/tools/buildman/requirements.txt
> UBOOT_DEPENDENCIES += \
> host-python-jsonschema \
> - host-python-pyyaml
> + host-python-pyyaml \
> + host-python-yamllint
> UBOOT_MAKE_OPTS += BINMAN_INDIRS=$(BINARIES_DIR)
> endif
>
> --
> 2.39.2
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-04-12 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 5:53 [Buildroot] [PATCH v3 1/3] package/python-yamllint: new package Heiko Thiery
2024-04-12 5:53 ` [Buildroot] [PATCH v3 2/3] boot/ti-k3-r5-loader: add dependency to yamllint Heiko Thiery
2024-04-12 15:18 ` Bryan Brattlof via buildroot
2024-04-12 5:54 ` [Buildroot] [PATCH v3 3/3] uboot/uboot: add new " Heiko Thiery
2024-04-12 15:18 ` Bryan Brattlof via buildroot [this message]
2024-04-12 15:43 ` [Buildroot] [PATCH v3 1/3] package/python-yamllint: new package Yann E. MORIN
2024-04-12 15:51 ` Yann E. MORIN
2024-04-12 20:54 ` Romain Naour
2024-04-13 7:20 ` Heiko Thiery
2024-05-07 16:00 ` Peter Korsgaard
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=20240412151811.cty2f2uiwig2hiyd@bryanbrattlof.com \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=asafka7@gmail.com \
--cc=bb@ti.com \
--cc=gadiyar@ti.com \
--cc=heiko.thiery@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
/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.