From: Krzysztof Kozlowski <krzk@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>
Cc: Stefan Wahren <wahrenst@gmx.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
bcm-kernel-feedback-list@broadcom.com, kernel-dev@igalia.com,
Ulf Hansson <ulf.hansson@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Fix V3D deferred probe timeout
Date: Mon, 17 Nov 2025 09:04:52 +0100 [thread overview]
Message-ID: <7e498feb-15a2-4688-acfb-15021026f5c0@kernel.org> (raw)
In-Reply-To: <aRoQa80RE_3yAoTI@sirena.co.uk>
On 16/11/2025 18:56, Mark Brown wrote:
> On Sun, Nov 16, 2025 at 09:14:39AM -0800, Florian Fainelli wrote:
>> On 11/16/2025 5:52 AM, Mark Brown wrote:
>
>>> Yes, it seems to work. Given that this patch was applied I had been
>>> expecting it to show up in -next but that doesn't seem to be the case?
>
>> It was applied on Nov 14th:
>
>> https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git/commit/?id=020e792ca39b
>
> Ah, that's the pull request you sent with it in getting pulled in to the
> main SoC tree. I was expecting your tree to be in -next directly as
> well (a lot of individual SoC trees are) so when you applied it on the
And every individual maintainer's SoC tree should be there... There is
an exception for media because their upstream does not pull from
sub-maintainers but rebases, which would lead to duplicated commits, but
that not the case for SoC tree.
> 4th it'd start appearing.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-11-17 8:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 17:45 [PATCH] arm64: defconfig: Fix V3D deferred probe timeout Stefan Wahren
2025-11-04 22:20 ` Florian Fainelli
2025-11-12 17:20 ` Stefan Wahren
2025-11-16 13:52 ` Mark Brown
2025-11-16 17:14 ` Florian Fainelli
2025-11-16 17:56 ` Mark Brown
2025-11-17 8:04 ` 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=7e498feb-15a2-4688-acfb-15021026f5c0@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=florian.fainelli@broadcom.com \
--cc=kernel-dev@igalia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=wahrenst@gmx.net \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.