[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20251229121440-55a7d82a-6fd9-4875-9399-ab6b3ab05740@linutronix.de>
Date: Mon, 29 Dec 2025 12:16:10 +0100
From: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
To: Simon Glass <sjg@...omium.org>
Cc: linux-arm-kernel@...ts.infradead.org,
Masahiro Yamada <masahiroy@...nel.org>, Chen-Yu Tsai <wenst@...omium.org>,
Nicolas Schier <nicolas@...sle.eu>, J . Neuschäfer <j.ne@...teo.net>,
Ahmad Fatoum <a.fatoum@...gutronix.de>, Tom Rini <trini@...sulko.com>, Alice Ryhl <aliceryhl@...gle.com>,
Ard Biesheuvel <ardb@...nel.org>, Ingo Molnar <mingo@...nel.org>,
Josh Poimboeuf <jpoimboe@...nel.org>, Kees Cook <kees@...nel.org>,
Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nsc@...nel.org>,
Oleh Zadorozhnyi <lesorubshayan@...il.com>, Petr Mladek <pmladek@...e.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 4/6] kbuild: Support a MAKE_FIT_FLAGS environment
variable
On Sat, Dec 27, 2025 at 07:21:48AM -0700, Simon Glass wrote:
> In some cases it is useful to be able to pass additional flags to the
> make_fit.py script. For example, since ramdisks are typically large,
> passing -E to use external data can be helpful.
>
> Add a new MAKE_FIT_FLAGS variable for this.
The new variable's name is a bit inconsistent with the other ones.
I would have used `FIT_EXTRA_ARGUMENTS` or such.
> Signed-off-by: Simon Glass <sjg@...omium.org>
In any case:
Reviewed-by: Thomas Weißschuh <thomas.weissschuh@...utronix.de>
Powered by blists - more mailing lists