linux-kernel - Re: [PATCH] MIPS: dts: Always descend vendor subdirectories

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aS1jCDNfAFrGZzT2@alpha.franken.de>
Date: Mon, 1 Dec 2025 10:42:32 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: "Rob Herring (Arm)" <robh@...nel.org>
Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org,
	linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MIPS: dts: Always descend vendor subdirectories

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@...nel.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 ]