U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: liulhong617@163.com, u-boot@lists.denx.de
Subject: Re: [PATCH v2] Makefile: depend on OF_LIST dts sources for fit-dtb.blob
Date: Fri, 17 Jul 2026 11:34:38 -0600	[thread overview]
Message-ID: <20260717173438.GT749385@bill-the-cat> (raw)
In-Reply-To: <CAFLszTjMJq2C02Xc0YTX0+5Q-DOPK+zrKn62PwU1qE+vPBASCw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]

On Fri, Jul 17, 2026 at 08:11:42AM -0600, Simon Glass wrote:
> Hi Lianghong,
> 
> On 2026-07-13T07:45:39, lianghong617 <liulhong617@163.com> wrote:
> > Makefile: depend on OF_LIST dts sources for fit-dtb.blob
> >
> > When CONFIG_MULTI_DTB_FIT is enabled, fit-dtb.blob is produced by
> > mkimage with one "-b <dtb>" argument for every entry in
> > CONFIG_OF_LIST.  The make rule, however, only listed dts/dt.dtb
> > (i.e. the CONFIG_DEFAULT_DEVICE_TREE blob) as a prerequisite:
> >
> >   fit-dtb.blob: dts/dt.dtb FORCE
> >       $(call if_changed,mkimage)
> >
> > Because FORCE is PHONY, if_changed ignores it and rebuilds only when
> > any-prereq or arg-check is non-empty.  Editing a non-default dts in
> > OF_LIST rebuilds its .dtb (tracked correctly via fixdep), but that
> > .dtb was not a prerequisite of fit-dtb.blob, so $? stayed empty; the
> > mkimage command line was unchanged too, so arg-check was empty as
> > well.  if_changed therefore skipped mkimage and fit-dtb.blob kept the
> > stale dtbs.  u-boot.bin, which appends fit-dtb.blob, then shipped the
> > old device tree and the dts change did not take effect.
> >
> > A previous attempt to fix this added every OF_LIST .dtb *output* as a
> > [...]
> >
> > Makefile | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> > Signed-off-by: lianghong617 <liulhong617@163.com>
> 
> Please can you use your real name in the Signed-off-by tag? Also we
> don't normally use bullet points in a commit message.

We don't (nor does the linux kernel) have a "real name" policy.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-07-17 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  7:45 [PATCH v2] Makefile: depend on OF_LIST dts sources for fit-dtb.blob lianghong617
2026-07-17 14:11 ` Simon Glass
2026-07-17 17:34   ` Tom Rini [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=20260717173438.GT749385@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=liulhong617@163.com \
    --cc=sjg@chromium.org \
    --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