From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sreeshankar K <sreeshankar0910@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
andersson@kernel.org, konradybcio@kernel.org, tglx@kernel.org
Cc: lpieralisi@kernel.org, robimarko@gmail.com, linux@gurudas.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 5/5] dt-bindings: interrupt-controller: qcom,pdc: Document SM7250 PDC
Date: Mon, 17 Aug 2026 10:07:02 +0200 [thread overview]
Message-ID: <a90868d4-1411-42bf-b42e-f517541187ae@kernel.org> (raw)
In-Reply-To: <20260816161808.12419-6-sreeshankar0910@gmail.com>
On 16/08/2026 18:18, Sreeshankar K wrote:
> Document the PDC block on the SM7250 SoC.
>
> Signed-off-by: Sreeshankar K <sreeshankar0910@gmail.com>
> ---
> .../devicetree/bindings/interrupt-controller/qcom,pdc.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Please organize the patch documenting the compatible (DT bindings)
before the patch using that compatible.
See also:
https://elixir.bootlin.com/linux/v6.14-rc6/source/Documentation/devicetree/bindings/submitting-patches.rst#L46
Best regards,
Krzysztof
prev parent reply other threads:[~2026-08-17 8:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-16 16:18 [PATCH v2 0/5] Add SM7250 base dts file Sreeshankar K
2026-08-16 16:18 ` [PATCH v2 1/5] arm64: dts: qcom: " Sreeshankar K
2026-08-16 16:33 ` sashiko-bot
2026-08-17 1:12 ` Dmitry Baryshkov
2026-08-17 8:06 ` Krzysztof Kozlowski
2026-08-16 16:18 ` [PATCH v2 2/5] dt-bindings: arm: cpus: Document Kryo 475 CPUs Sreeshankar K
2026-08-16 16:18 ` [PATCH v2 3/5] dt-bindings: arm: qcom: Document SM7250 SoC and boards Sreeshankar K
2026-08-17 8:06 ` Krzysztof Kozlowski
2026-08-16 16:18 ` [PATCH v2 4/5] dt-bindings: firmware: qcom,scm: Document SM7250 SCM Sreeshankar K
2026-08-16 16:18 ` [PATCH v2 5/5] dt-bindings: interrupt-controller: qcom,pdc: Document SM7250 PDC Sreeshankar K
2026-08-17 8:07 ` 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=a90868d4-1411-42bf-b42e-f517541187ae@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@gurudas.dev \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--cc=sreeshankar0910@gmail.com \
--cc=tglx@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