From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Rob Herring <robh@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warnings after merge of the devicetree tree
Date: Mon, 5 Jan 2026 16:44:50 +1100 [thread overview]
Message-ID: <20260105164450.0bce20bd@canb.auug.org.au> (raw)
In-Reply-To: <CAL_JsqJw+b=Ro1=cz7wMwwUdPr9eE3C=Snr0skYwTjn1RjX5cg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2094 bytes --]
Hi Rob,
On Fri, 28 Nov 2025 08:54:34 -0600 Rob Herring <robh@kernel•org> wrote:
>
> On Thu, Nov 27, 2025 at 11:10 PM Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> >
> > On Tue, 18 Nov 2025 14:38:43 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > >
> > > Hi all,
> > >
> > > After merging the devicetree tree, today's linux-next build (arm64
> > > defconfig) produced these warnings:
> > >
> > > scripts/Makefile.dtbs:20: .dtbo is not applied to any base: rp1.dtbo
> > > scripts/Makefile.dtbs:20: .dtbo is not applied to any base: mt7986a-bananapi-bpi-r3-emmc.dtbo mt7986a-bananapi-bpi-r3-nand.dtbo mt7986a-bananapi-bpi-r3-nor.dtbo mt7986a-bananapi-bpi-r3-sata.dtbo mt7986a-bananapi-bpi-r3-sd.dtbo mt7988a-bananapi-bpi-r4-emmc.dtbo mt7988a-bananapi-bpi-r4-pro-cn15.dtbo mt7988a-bananapi-bpi-r4-pro-cn18.dtbo mt7988a-bananapi-bpi-r4-pro-emmc.dtbo mt7988a-bananapi-bpi-r4-pro-sd.dtbo mt7988a-bananapi-bpi-r4-sd.dtbo mt8395-radxa-nio-12l-8-hd-panel.dtbo
> > > scripts/Makefile.dtbs:20: .dtbo is not applied to any base: k3-am62x-phyboard-lyra-gpio-fan.dtbo k3-am62-lp-sk-nand.dtbo k3-am642-phyboard-electra-gpio-fan.dtbo k3-am642-phyboard-electra-pcie-usb2.dtbo k3-am642-phyboard-electra-x27-gpio1-spi1-uart3.dtbo k3-am642-phyboard-electra-peb-c-010.dtbo k3-am6xx-phycore-disable-eth-phy.dtbo k3-am6xx-phycore-disable-rtc.dtbo k3-am6xx-phycore-disable-spi-nor.dtbo k3-am6xx-phycore-qspi-nor.dtbo k3-j721e-evm-gesi-exp-board.dtbo k3-am67a-kontron-sa67-gpios.dtbo
> > >
> > > Exposed by commit
> > >
> > > d8c8a575f5aa ("kbuild: Ensure .dtbo targets are applied to a base .dtb")
> >
> > I am still seeing these warnings.
>
> Patches are posted to fix all of them[1][2][3].
>
> Rob
>
> [1] https://lore.kernel.org/all/20251117211503.728354-2-robh@kernel.org/
> [2] https://lore.kernel.org/all/20251117211306.725678-1-robh@kernel.org/
> [3] https://lore.kernel.org/all/20251117211316.725960-1-robh@kernel.org/
Today, we are down to just
scripts/Makefile.dtbs:20: .dtbo is not applied to any base: rp1.dtbo
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-01-05 5:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 3:38 linux-next: build warnings after merge of the devicetree tree Stephen Rothwell
2025-11-28 5:10 ` Stephen Rothwell
2025-11-28 14:54 ` Rob Herring
2025-11-28 22:31 ` Stephen Rothwell
2025-12-16 1:19 ` Stephen Rothwell
2025-12-18 10:15 ` Stephen Rothwell
2025-12-18 13:06 ` Rob Herring
2026-01-05 5:44 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-15 4:32 Stephen Rothwell
2022-01-15 11:33 ` Michael Walle
2021-03-29 8:53 Stephen Rothwell
2021-03-29 9:48 ` Lee Jones
2020-03-16 1:11 Stephen Rothwell
2018-09-20 1:47 Stephen Rothwell
2018-09-20 13:49 ` Rob Herring
2018-09-05 0:39 Stephen Rothwell
2018-09-05 1:54 ` Stephen Rothwell
2018-09-05 11:20 ` Rob Herring
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=20260105164450.0bce20bd@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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