public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rasmus Villemoes <ravi@prevas.dk>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de,  Tom Rini <trini@konsulko.com>,
	 Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	 Adriano Cordova <adrianox@gmail.com>,
	Greg Malysa <malysagreg@gmail.com>,
	 James Hilliard <james.hilliard1@gmail.com>,
	 Marek Vasut <marek.vasut+renesas@mailbox.org>,
	 Philip Molloy <philip.molloy@analog.com>,
	 Richard Genoud <richard.genoud@bootlin.com>,
	Sughosh Ganu <sughosh.ganu@arm.com>,
	 Tien Fong Chee <tien.fong.chee@altera.com>
Subject: Re: [PATCH v4 1/2] kbuild: Move U-Boot .incbin rules to Makefile.lib-u-boot
Date: Mon, 13 Apr 2026 23:16:14 +0200	[thread overview]
Message-ID: <87mrz6muht.fsf@prevas.dk> (raw)
In-Reply-To: <20260413131541.2091541-1-sjg@chromium.org> (Simon Glass's message of "Mon, 13 Apr 2026 07:15:37 -0600")

On Mon, Apr 13 2026, Simon Glass <sjg@chromium.org> wrote:

> The font, splash-screen and EFI .incbin wrapper rules are U-Boot
> additions that do not exist in the upstream Linux kbuild. Keeping them
> in scripts/Makefile.lib makes re-syncing with Linux harder than it needs
> to be, as every sync must manually preserve the U-Boot additions.
>
> Move these rules into a new scripts/Makefile.lib-u-boot and include it
> from Makefile.build and Makefile.xpl, right after the existing
> Makefile.lib include.
>
> This is a pure code-move with no functional change.
>
> Suggested-by: Tom Rini <trini@konsulko.com>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> Acked-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>

Reviewed-by: Rasmus Villemoes <ravi@prevas.dk>

      parent reply	other threads:[~2026-04-13 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 13:15 [PATCH v4 1/2] kbuild: Move U-Boot .incbin rules to Makefile.lib-u-boot Simon Glass
2026-04-13 13:15 ` [PATCH v4 2/2] kbuild: Use if_changed for font and splash .incbin rules Simon Glass
2026-04-13 21:16   ` Rasmus Villemoes
2026-04-13 21:16 ` Rasmus Villemoes [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=87mrz6muht.fsf@prevas.dk \
    --to=ravi@prevas.dk \
    --cc=adrianox@gmail.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=james.hilliard1@gmail.com \
    --cc=malysagreg@gmail.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=philip.molloy@analog.com \
    --cc=richard.genoud@bootlin.com \
    --cc=sjg@chromium.org \
    --cc=sughosh.ganu@arm.com \
    --cc=tien.fong.chee@altera.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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