From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>,
christoph.muellner@theobroma-systems.com,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot/uboot: add option to define custom dependencies
Date: Sat, 8 Jan 2022 20:40:22 +0100 [thread overview]
Message-ID: <20220108204022.550a7909@windsurf> (raw)
In-Reply-To: <20200425000629.2068191-1-heiko@sntech.de>
Hello Heiko,
On Sat, 25 Apr 2020 02:06:29 +0200
Heiko Stuebner <heiko@sntech.de> wrote:
> From: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
>
> A custom uboot version my depend on additional unspecified packages
> to be built before the uboot build is attempted.
>
> One example is an additional config fragment referencing things
> from other packages, so add an option similar to the config fragments
> where these can be defined.
>
> Signed-off-by: Heiko Stuebner <heiko.stuebner@theobroma-systems.com>
> ---
> boot/uboot/Config.in | 8 ++++++++
> boot/uboot/uboot.mk | 1 +
> 2 files changed, 9 insertions(+)
Sorry to come back to you so long after the patch was submitted. We
finally had a discussion, and decided that we would prefer to see the
actual practical use cases of this, before merging this option. Maybe
this option is a good idea, but we really want to hear about specific
use cases first. If you have one, we're definitely interested to hear
about it!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-01-08 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 0:06 [Buildroot] [PATCH] boot/uboot: add option to define custom dependencies Heiko Stuebner
2020-04-25 13:38 ` Thomas Petazzoni
2020-04-25 21:13 ` Yann E. MORIN
2020-04-25 21:22 ` Thomas Petazzoni
2020-04-25 21:31 ` Heiko Stübner
2020-04-25 21:45 ` Yann E. MORIN
2020-04-27 8:31 ` Arnout Vandecappelle
2020-04-27 15:41 ` Thomas Petazzoni
2020-04-27 16:59 ` Arnout Vandecappelle
[not found] ` <794007695.ejsOJfsjEF@diego>
2020-04-27 19:08 ` Thomas Petazzoni
2022-01-08 19:40 ` Thomas Petazzoni [this message]
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=20220108204022.550a7909@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=christoph.muellner@theobroma-systems.com \
--cc=heiko.stuebner@theobroma-systems.com \
--cc=heiko@sntech.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