From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Abel Vesa <abel.vesa@oss.qualcomm.com>,
Georgi Djakov <djakov@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Odelu Kukatla <odelu.kukatla@oss.qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: interconnect: qcom,eliza-rpmh: Add SDCC1 slave
Date: Thu, 14 May 2026 07:44:12 +0200 [thread overview]
Message-ID: <5c615bdc-3a19-4f07-a38d-16d45f318411@oss.qualcomm.com> (raw)
In-Reply-To: <20260512-eliza-interconnect-add-missing-sdcc1-slave-node-v1-1-b1edf81bac3b@oss.qualcomm.com>
On 12/05/2026 14:18, Abel Vesa wrote:
> The Eliza RPMh interconnect binding is missing the SDCC1 CNOC CFG
> slave ID. Add it so SDCC1 consumer can describe the corresponding
> interconnect path.
>
> Append the new ID to preserve the existing ABI values.
>
> Fixes: 8300438dc424 ("dt-bindings: interconnect: document the RPMh Network-On-Chip interconnect in Eliza SoC")
No bug here to be fixed. Incomplete first posting is not buggy just
because it is incomplete. Otherwise please provide more details about
the bug in commit msg - why initial posting could not even work
(although it did work...).
Same for second commit.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-05-14 5:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 12:18 [PATCH 0/2] interconnect: qcom: eliza: Add missing SDCC1 slave Abel Vesa
2026-05-12 12:18 ` [PATCH 1/2] dt-bindings: interconnect: qcom,eliza-rpmh: Add " Abel Vesa
2026-05-14 5:44 ` Krzysztof Kozlowski [this message]
2026-05-14 10:46 ` Abel Vesa
2026-05-14 11:44 ` Krzysztof Kozlowski
2026-05-14 12:03 ` Abel Vesa
2026-05-12 12:18 ` [PATCH 2/2] interconnect: qcom: eliza: Add SDCC1 slave node Abel Vesa
2026-05-13 14:24 ` Dmitry Baryshkov
2026-05-13 21:17 ` sashiko-bot
2026-05-14 9:52 ` Georgi Djakov
2026-05-14 10:39 ` Abel Vesa
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=5c615bdc-3a19-4f07-a38d-16d45f318411@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=abel.vesa@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=odelu.kukatla@oss.qualcomm.com \
--cc=robh@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