From: Krzysztof Kozlowski <krzk@kernel.org>
To: Michael Walle <mwalle@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: soc@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: defconfig: make TPS6594 support build-in
Date: Fri, 21 Nov 2025 09:10:04 +0100 [thread overview]
Message-ID: <c55c87ea-01a1-4200-8fed-e629d7d068ec@kernel.org> (raw)
In-Reply-To: <DEE7CKFYFS69.2R2RADO7WNTFS@kernel.org>
On 21/11/2025 08:42, Michael Walle wrote:
> On Thu Nov 20, 2025 at 2:51 PM CET, Krzysztof Kozlowski wrote:
>> On 20/11/2025 08:55, Michael Walle wrote:
>>> The Kontron SMARC-sAM67 module needs the TPS6594 regulator driver to
>>> boot from SD card, i.e. for its root filesystem.
>>>
>>> Signed-off-by: Michael Walle <mwalle@kernel.org>
>>> ---
>>> Arnd, the PR from TI [1] (which contains the device trees for this
>>> board) is already out, so I'm sending this to the soc ML directly.
>>> Let me know if this can still be applied, if not, I'll have to wait
>>> for the next window.
>>>
>>
>> Why it cannot go via TI tree? It should...
>
> As explained above it can of course, but I've missed the time window
> as the PR from the TI tree to the soc tree was already sent out.
This alone would justify for anyone to send directly to soc@ when they
miss their upstream maintainer timeframes, so sorry, but that's the way.
Time window in TI can still take it. If they cannot, then for sure soc@
cannot, because soc@ takes from TI.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-21 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 7:55 [PATCH] arm64: defconfig: make TPS6594 support build-in Michael Walle
2025-11-20 13:51 ` Krzysztof Kozlowski
2025-11-21 7:42 ` Michael Walle
2025-11-21 8:10 ` Krzysztof Kozlowski [this message]
2025-11-21 9:02 ` Michael Walle
2025-11-21 8:11 ` Krzysztof Kozlowski
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=c55c87ea-01a1-4200-8fed-e629d7d068ec@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=soc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox