All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Nicolas Schier <nsc@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix compilation of dtb specified on command-line without make rule
Date: Tue, 25 Nov 2025 11:52:38 +0100	[thread overview]
Message-ID: <aSWKdgypKqt1Mq_J@L-PF2SHBMP> (raw)
In-Reply-To: <20251124130747.GA3957523-robh@kernel.org>

On Mon, Nov 24, 2025 at 07:07:47AM -0600, Rob Herring wrote:
> On Thu, Nov 20, 2025 at 03:06:43PM +0100, Thomas De Schampheleire wrote:
[...]
> > In this scenario, both 'dtb-y' and 'dtb-' are empty, and the inclusion of
> > scripts/Makefile.dtbs relies on 'targets' to contain the MAKECMDGOALS. The
> > value of 'targets', however, is only final later in the code.
> >
> > Move the conditional include of scripts/Makefile.dtbs down to where the
> > value of 'targets' is final.
> 
> This breaks 'make dtbs' (and just 'make' for arm64).

I see the 'make dtbs' failure, I will investigate.

I don't yet see a problem with 'make ARCH=arm64 CROSS_COMPILE=[...]' after a
standard 'defconfig'. Can you please clarify how it fails for you?

Thanks,
Thomas

  reply	other threads:[~2025-11-25 10:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 14:06 [PATCH] kbuild: fix compilation of dtb specified on command-line without make rule Thomas De Schampheleire
2025-11-21  6:42 ` Nathan Chancellor
2025-11-21 19:46   ` Nicolas Schier
2025-11-24 13:07 ` Rob Herring
2025-11-25 10:52   ` Thomas De Schampheleire [this message]
2025-11-25 13:25     ` Rob Herring
  -- strict thread matches above, loose matches on Subject: below --
2025-11-20 15:18 kernel test robot
2025-11-20 15:29 kernel test robot

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=aSWKdgypKqt1Mq_J@L-PF2SHBMP \
    --to=thomas.de_schampheleire@nokia.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=robh@kernel.org \
    /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.