From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: yann.morin@orange.com, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, buildroot@buildroot.org,
brandon.maier@collins.com, fiona.klute@gmx.de, ju.o@free.fr,
romain.naour@smile.fr, michal.simek@amd.com,
romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v3 1/3] linux/linux.mk: export LINUX_DTBS
Date: Wed, 4 Mar 2026 19:00:21 +0100 [thread overview]
Message-ID: <aahzAZ47FxSAGgEF@windsurf> (raw)
In-Reply-To: <20260304152057.3465672-1-neal.frager@amd.com>
On Wed, Mar 04, 2026 at 03:20:55PM +0000, Neal Frager wrote:
> LINUX_DTBS = $(addsuffix .dtb,$(LINUX_DTS_NAME)) $(addsuffix .dtbo,$(LINUX_DTSO_NAMES))
> +# Post-build scripts may need to reference the LINUX_DTBS,
> +# so export it so it is easier to use
> +export LINUX_DTBS
I find this a bit "meh". What about using "make VARS=LINUX_DTBS
printvars" or "make VARS=LINUX_DTBS show-vars" from your post-build
script?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-03-04 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 15:20 [Buildroot] [PATCH v3 1/3] linux/linux.mk: export LINUX_DTBS Neal Frager via buildroot
2026-03-04 15:20 ` [Buildroot] [PATCH v3 2/3] board/zynqmp/post-image.sh: use LINUX_DTBS variable Neal Frager via buildroot
2026-03-04 15:20 ` [Buildroot] [PATCH v3 3/3] board/versal/post-image.sh: " Neal Frager via buildroot
2026-03-04 18:00 ` Thomas Petazzoni via buildroot [this message]
2026-03-05 10:08 ` [Buildroot] [PATCH v3 1/3] linux/linux.mk: export LINUX_DTBS Frager, Neal via buildroot
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=aahzAZ47FxSAGgEF@windsurf \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=fiona.klute@gmx.de \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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.