From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Paul Cercueil <paul@crapouillou.net>,
Rob Herring <robh@kernel.org>,
UNGLinuxDriver@microchip.com, devicetree@vger.kernel.org
Subject: Re: [PATCH] MIPS: migrate to generic rule for built-in DTBs
Date: Sat, 11 Jan 2025 14:17:14 +0100 [thread overview]
Message-ID: <Z4JvWqZQgsw6tZZ6@alpha.franken.de> (raw)
In-Reply-To: <20241222000416.2577633-1-masahiroy@kernel.org>
On Sun, Dec 22, 2024 at 09:04:13AM +0900, Masahiro Yamada wrote:
> Commit 654102df2ac2 ("kbuild: add generic support for built-in boot
> DTBs") introduced generic support for built-in DTBs.
>
> Select GENERIC_BUILTIN_DTB and BUILTIN_DTB_ALL when the built-in DTB
> support is enabled.
>
> DTBs compiled under arch/mips/boot/dts/ will be wrapped by the generic
> rule in scripts/Makefile.vmlinux.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> arch/mips/Kconfig | 2 ++
> arch/mips/Makefile | 3 ---
> arch/mips/boot/dts/Makefile | 2 --
> arch/mips/boot/dts/brcm/Makefile | 2 --
> arch/mips/boot/dts/cavium-octeon/Makefile | 2 --
> arch/mips/boot/dts/ingenic/Makefile | 2 --
> arch/mips/boot/dts/lantiq/Makefile | 2 --
> arch/mips/boot/dts/loongson/Makefile | 2 --
> arch/mips/boot/dts/mscc/Makefile | 3 ---
> arch/mips/boot/dts/mti/Makefile | 2 --
> arch/mips/boot/dts/pic32/Makefile | 2 --
> arch/mips/boot/dts/ralink/Makefile | 2 --
> 12 files changed, 2 insertions(+), 24 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 ]
prev parent reply other threads:[~2025-01-11 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 0:04 Masahiro Yamada
2025-01-11 13:17 ` 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=Z4JvWqZQgsw6tZZ6@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--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=masahiroy@kernel.org \
--cc=paul@crapouillou.net \
--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
all inboxes | Powered by JetHome®