From: Krzysztof Kozlowski <krzk@kernel.org>
To: Qingqing Zhou <quic_qqzhou@quicinc.com>,
andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, robimarko@gmail.com,
will@kernel.org, robin.murphy@arm.com, joro@8bytes.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Subject: Re: [PATCH v2 1/4] dt-bindings: firmware: qcom,scm: document QCS615 SCM
Date: Tue, 15 Oct 2024 10:21:57 +0200 [thread overview]
Message-ID: <a08e76a7-8e68-4ae6-9b83-67e5d20468b9@kernel.org> (raw)
In-Reply-To: <20241015081603.30643-2-quic_qqzhou@quicinc.com>
On 15/10/2024 10:16, Qingqing Zhou wrote:
> Add the compatible for Qualcomm QCS615 SCM.
>
> Signed-off-by: Qingqing Zhou <quic_qqzhou@quicinc.com>
I give up on this.
Please reach internally to get proper guidance how to send patches and
what to do with tags.
I am not going to do the work twice.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-15 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 8:15 [PATCH v2 0/4] Add support for APPS SMMU on QCS615 Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 1/4] dt-bindings: firmware: qcom,scm: document QCS615 SCM Qingqing Zhou
2024-10-15 8:21 ` Krzysztof Kozlowski [this message]
2024-10-15 8:50 ` Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 2/4] dt-bindings: arm-smmu: document QCS615 APPS SMMU Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 3/4] arm64: dts: qcom: qcs615: add the SCM node Qingqing Zhou
2024-10-15 8:16 ` [PATCH v2 4/4] arm64: dts: qcom: qcs615: add the APPS SMMU node Qingqing Zhou
2024-10-17 20:05 ` Konrad Dybcio
2024-10-18 6:20 ` Qingqing Zhou
2024-10-23 5:48 ` Qingqing Zhou
2024-10-25 17:26 ` Konrad Dybcio
2024-10-15 8:20 ` [PATCH v2 0/4] Add support for APPS SMMU on QCS615 Krzysztof Kozlowski
2024-10-15 9:53 ` Qingqing Zhou
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=a08e76a7-8e68-4ae6-9b83-67e5d20468b9@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_qqzhou@quicinc.com \
--cc=robh@kernel.org \
--cc=robimarko@gmail.com \
--cc=robin.murphy@arm.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).