From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Hardeep Sharma <hardeep.sharma@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: kernel@quicinc.com, kernel@oss.qualcomm.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] soc: qcom: geni-se: allow selection on 32-bit ARM Qualcomm SoCs
Date: Wed, 29 Jul 2026 12:45:01 +0200 [thread overview]
Message-ID: <32b6fb33-0e80-4e7e-86ab-12730744ef32@oss.qualcomm.com> (raw)
In-Reply-To: <e861a5b4-38a3-4f39-932e-558188b5438f@oss.qualcomm.com>
On 29/07/2026 12:28, Hardeep Sharma wrote:
>
> On 7/29/2026 3:30 PM, Krzysztof Kozlowski wrote:
>> This gives me nothing:
>> $ git grep kuno
>>
>> Are you sure you organized your patches correctly?
>>
>> Best regards,
>> Krzysztof
> Hi Krzysztof,
>
> You're right — the Kuno support series isn't upstream yet.
>
> I'm planning to upstream the Kuno support series shortly, and this
> Kconfig fix is a prerequisite for it (without it, QCOM_GENI_SE — and
> therefore the debug UART — is unselectable on 32-bit ARM).
It is not a prerequisite if there is no Kuno.
>
> What would you suggest — should I fold this fix into the Kuno
> series as patch 1, or keep it standalone and let the kuno series
> depend on it?
Organize your work in logical chunks, please read submitting patches. We
also discussed this many times in internal forums/chats. Even discussing
EXACTLY now.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-07-29 10:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 9:34 Hardeep Sharma
2026-07-29 10:00 ` Krzysztof Kozlowski
2026-07-29 10:28 ` Hardeep Sharma
2026-07-29 10:45 ` Krzysztof Kozlowski [this message]
2026-07-29 10:48 ` 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=32b6fb33-0e80-4e7e-86ab-12730744ef32@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=hardeep.sharma@oss.qualcomm.com \
--cc=kernel@oss.qualcomm.com \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®