public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: dts: Always descend vendor subdirectories
Date: Mon, 1 Dec 2025 10:42:32 +0100	[thread overview]
Message-ID: <aS1jCDNfAFrGZzT2@alpha.franken.de> (raw)
In-Reply-To: <20251120204717.1982418-1-robh@kernel.org>

On Thu, Nov 20, 2025 at 02:47:16PM -0600, Rob Herring (Arm) wrote:
> Commit 41528ba6afe6 ("MIPS: DTS: Only build subdir of current platform")
> broke building of all DTBs when CONFIG_OF_ALL_DTBS is enabled unless all
> the various kconfig options were also enabled. The only effect that commit
> had was getting rid of some harmless build lines such as:
> 
>       AR      arch/mips/boot/dts/mti/built-in.a
> 
> Those lines were part of the built-in DTB support. Since commit
> 04e4ec98e405 ("MIPS: migrate to generic rule for built-in DTBs"), how the
> built-in DTBs are handled has changed and those lines are no longer
> generated, so revert to the prior behavior.
> 
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
>  arch/mips/boot/dts/Makefile         | 35 +++++++++++++----------------
>  arch/mips/boot/dts/realtek/Makefile |  4 ++--
>  2 files changed, 18 insertions(+), 21 deletions(-)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2025-12-01  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 20:47 [PATCH] MIPS: dts: Always descend vendor subdirectories Rob Herring (Arm)
2025-12-01  9:42 ` Thomas Bogendoerfer [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=aS1jCDNfAFrGZzT2@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox