[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <a7fa4971-85a3-4435-8728-493acb68ed0d@app.fastmail.com>
Date: Fri, 03 Oct 2025 00:40:53 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Krzysztof Kozlowski" <krzk@...nel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@...aro.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
linux-arm-kernel@...ts.infradead.org, linux-riscv@...ts.infradead.org,
soc@...ts.linux.dev
Subject: Re: [GIT PULL 2/5] soc: dt changes for 6.18
On Thu, Oct 2, 2025, at 08:26, Krzysztof Kozlowski wrote:
> On Thu, 2 Oct 2025 at 15:04, Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> wrote:
>> On Wed, 1 Oct 2025 at 15:27, Arnd Bergmann <arnd@...db.de> wrote:
>> >
>> > https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/soc-dt-6.18
>>
>> Bah. I've merged this, but this causes build failures on arm64.
>>
>> I only noticed after already having pushed it out.
>>
>> > SeonGu Kang (1):
>> > arm64: dts: axis: Add ARTPEC-8 Grizzly dts support
>
>
> I'm sorry, I should not have trusted contributors from Samsung that
> they know what they are doing and I think my CI misses allyesconfig on
> particular branches, because for-next branch did enable this symbol
> and it was tested by my CI. Also LKP tests each of my branches and
> didn't report this, I think.
This one is on me really, I had the right tooling available and
I had used it in the past, but I never ran it after I did the
bulk of the merges in the past few weeks. There is always someone
who misses a dependency in the DT updates and I rely on that
check anyway to detect some types of incompatible binding updates
and I have no excuse for not noticing it myself.
We'll have to refine the process anyway when we start taking turns
with the soc tree merges.
> Issue will be fixed with commit coming via clk tree - Stephen Boyd:
> https://lore.kernel.org/linux-samsung-soc/20250825114436.46882-2-ravi.patel@samsung.com/
> And git pull:
> https://lore.kernel.org/all/20250909183504.104261-2-krzysztof.kozlowski@linaro.org/
>
> I understand this won't fix bisectability.
>
> Arnd,
> Eventually you can just mark arch-artpec as broken just to fix your branches.
The missing commit is at the bottom of your branch, so I'm sending
just that commit as a build fix, that seems easier than marking it
as broken now and then later reverting that change.
Arnd
Powered by blists - more mailing lists