From: "Arnd Bergmann" <arnd@arndb.de>
To: "Rob Herring" <robh@kernel.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: "Olof Johansson" <olof@lixom.net>,
ARM <linux-arm-kernel@lists.infradead.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the arm-soc-fixes tree
Date: Wed, 21 Feb 2024 14:59:36 +0100 [thread overview]
Message-ID: <ac9ddf79-6bc9-4daf-a271-82f8b3bca988@app.fastmail.com> (raw)
In-Reply-To: <CAL_JsqKw9OXb=aOMni1qprzeWDBgmjdJef-6VAjwx0R--D+URw@mail.gmail.com>
On Wed, Feb 21, 2024, at 14:53, Rob Herring wrote:
> On Tue, Feb 20, 2024 at 3:28 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>> arch/arm/boot/dts/renesas/r8a7793-gose.dtb: Warning (interrupt_map): Failed prerequisite 'interrupt_provider'
>>
>> Introduced/exposed by commit
>>
>> 78b6f8e7379b ("dtc: Enable dtc interrupt_provider check")
>>
>> I guess you missed some :-(
>
> No, Geert separately posted fixes for already.
I did make the mistake of applying the final patch "dtc:
Enable dtc interrupt_provider check" to the arm/fixes branch
for 6.8 along with the other fixes.
Clearly that should be separate and only go into mainline
after there are no more regressions, but now I'm unsure
about the other patches -- did you intend the dts fixes
for 6.8 or for the coming merge window?
Arnd
next prev parent reply other threads:[~2024-02-21 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 22:28 Stephen Rothwell
2024-02-21 5:30 ` Stephen Rothwell
2024-02-21 5:38 ` Stephen Rothwell
2024-02-21 13:58 ` Rob Herring
2024-02-21 14:42 ` Alexander Stein
2024-02-21 13:53 ` Rob Herring
2024-02-21 13:59 ` Arnd Bergmann [this message]
2024-02-21 14:27 ` Rob Herring
2024-02-21 14:51 ` Geert Uytterhoeven
2024-02-21 15:58 ` Arnd Bergmann
2024-02-21 16:36 ` Geert Uytterhoeven
2024-02-22 10:45 ` Geert Uytterhoeven
2024-02-21 14:01 ` Geert Uytterhoeven
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=ac9ddf79-6bc9-4daf-a271-82f8b3bca988@app.fastmail.com \
--to=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh@kernel.org \
--cc=sfr@canb.auug.org.au \
/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®