From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jie Gan <jie.gan@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: kaanapali: add coresight nodes
Date: Fri, 5 Dec 2025 14:21:30 +0100 [thread overview]
Message-ID: <f5186dc1-b16c-4cc7-9f36-37e179a85af9@oss.qualcomm.com> (raw)
In-Reply-To: <b08bfb85-3aa2-4fa9-afd7-a27c3f5e8a1a@oss.qualcomm.com>
On 12/5/25 2:18 PM, Jie Gan wrote:
>
>
> On 12/5/2025 7:20 PM, Konrad Dybcio wrote:
>> On 12/5/25 9:36 AM, Jie Gan wrote:
>>> Add CoreSight nodes to enable trace paths such as TPDM->ETF and STM->ETF.
>>> These devices are part of the AOSS, CDSP, QDSS, modem and some small
>>> subsystems, such as DCC, GCC, ipcc and so on.
>>>
>>> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
>>> ---
[...]
>> This list however should deter you from sending.. it's impossible for the
>> maintainers to resolve a list this long for you and there's a high chance
>> there will be changes/rebases required because any subset of these patches
>> you depend on may change during their reviews
>>
>
> Yes, that's the question. The good news is below two patch series already got reviewed.
>
> - gcc: https://lore.kernel.org/all/20251126-gcc_kaanapali-v3-v4-0-0fe73d6898e9@oss.qualcomm.com/
> - ipcc: https://lore.kernel.org/all/20251031-knp-ipcc-v3-0-62ffb4168dff@oss.qualcomm.com/
> Can I have your review-by tag after fix the order of the mentioned node?
> Then I will send a new version with the tag after the dependency is being cleaned.
Yes, with the order fixed please add my
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
prev parent reply other threads:[~2025-12-05 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 8:36 Jie Gan
2025-12-05 11:20 ` Konrad Dybcio
2025-12-05 13:18 ` Jie Gan
2025-12-05 13:21 ` Konrad Dybcio [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=f5186dc1-b16c-4cc7-9f36-37e179a85af9@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jie.gan@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@oss.qualcomm.com \
/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®