From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-riscv@lists.infradead.org, soc@lists.linux.dev
Subject: Re: [GIT PULL 2/5] soc: dt changes for 6.18
Date: Fri, 03 Oct 2025 00:40:53 +0200 [thread overview]
Message-ID: <a7fa4971-85a3-4435-8728-493acb68ed0d@app.fastmail.com> (raw)
In-Reply-To: <CAJKOXPcRw3teqahDc6RBCz8XvqLt2sHqxrOUxpA84RszcsnGFQ@mail.gmail.com>
On Thu, Oct 2, 2025, at 08:26, Krzysztof Kozlowski wrote:
> On Thu, 2 Oct 2025 at 15:04, Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
>> On Wed, 1 Oct 2025 at 15:27, Arnd Bergmann <arnd@arndb.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
next prev parent reply other threads:[~2025-10-02 22:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 22:23 [GIT PULL 0/5] soc: updates " Arnd Bergmann
2025-10-01 22:24 ` [GIT PULL 1/5] soc: new SoC support " Arnd Bergmann
2025-10-02 1:10 ` pr-tracker-bot
2025-10-01 22:26 ` [GIT PULL 2/5] soc: dt changes " Arnd Bergmann
2025-10-02 1:10 ` pr-tracker-bot
2025-10-02 4:43 ` Linus Torvalds
[not found] ` <CAGE=qrpygJ4XgtzdnGACj-6KRiD8r57F4ogNYaA3LLMusBV9fg@mail.gmail.com>
2025-10-02 6:26 ` Krzysztof Kozlowski
2025-10-02 22:40 ` Arnd Bergmann [this message]
2025-10-01 22:27 ` [GIT PULL 3/5] soc: defconfig updates " Arnd Bergmann
2025-10-02 1:10 ` pr-tracker-bot
2025-10-01 22:27 ` [GIT PULL 4/5] soc: driver " Arnd Bergmann
2025-10-02 1:10 ` pr-tracker-bot
2025-10-01 22:28 ` [GIT PULL 5/5] ARM: soc " Arnd Bergmann
2025-10-02 1:10 ` pr-tracker-bot
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=a7fa4971-85a3-4435-8728-493acb68ed0d@app.fastmail.com \
--to=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=soc@lists.linux.dev \
--cc=torvalds@linux-foundation.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®