From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dinh Nguyen <dinguyen@kernel.org>,
linux-arm-kernel@lists.infradead.org, soc@lists.linux.dev
Subject: Re: [GIT PULL] arm/arm64: dts: socfpga: updates for v6.20
Date: Fri, 13 Feb 2026 16:55:36 +0100 [thread overview]
Message-ID: <f26c16f9-b05b-48a8-9dba-57ee7f0710ee@kernel.org> (raw)
In-Reply-To: <2fe11d07-2b95-4c38-8cac-183fd88dabe9@kernel.org>
On 05/02/2026 09:49, Krzysztof Kozlowski wrote:
>>>
>>>
>>> These are not SoC patches, unless maintainers are unresponsive which I
>>> believe is not a case here, so they should not be going via this tree.
>>>
>>> None of this, merged on 15th Dec, was fed to linux-next, so you don't
>>> even know if this conflicts with maintainer trees thus pushing conflict
>>> discover unto soc tree.
>>>
>>> Not being in the next is already a problem but gets more serious when
>>> taking other subsystem patches.
>>>
>>> That's my comment, but Arnd was looking at these whether to merge.
>>>
>>
>> Apologies! I did not hear any feedback from those maintainers nor did I
>> remind them, so that's my fault. Let me rework this PR and take those
>> patches through the respective maintainer's tree.
>
>
> The bigger problem is that none of these were in the next. You need to
> solve this problem.
This still did not improve, at least as of yesterday's next.
Best regards,
Krzysztof
prev parent reply other threads:[~2026-02-13 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 20:01 [GIT PULL] arm/arm64: dts: socfpga: updates for v6.20 Dinh Nguyen
2026-01-28 18:48 ` Krzysztof Kozlowski
2026-01-30 12:12 ` Dinh Nguyen
2026-02-05 8:49 ` Krzysztof Kozlowski
2026-02-13 15:55 ` Krzysztof Kozlowski [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=f26c16f9-b05b-48a8-9dba-57ee7f0710ee@kernel.org \
--to=krzk@kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=soc@lists.linux.dev \
/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