From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Melody Olvera <quic_molvera@quicinc.com>,
Will Deacon <will@kernel.org>, Joerg Roedel <joro@8bytes.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm-smmu: Add compatible bindings for QDU1000 and QRU1000
Date: Sat, 15 Oct 2022 11:16:39 -0400 [thread overview]
Message-ID: <fd36ae9b-2f15-43a1-51dd-bed475f12e5b@linaro.org> (raw)
In-Reply-To: <20221014221051.7434-2-quic_molvera@quicinc.com>
On 14/10/2022 18:10, Melody Olvera wrote:
> Add compatible bindings for Qualcomm QDU1000 and QRU1000 platforms.
>
> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
> ---
> Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
> index 9066e6df1ba1..ae314436eddb 100644
> --- a/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
> +++ b/Documentation/devicetree/bindings/iommu/arm,smmu.yaml
> @@ -34,6 +34,8 @@ properties:
> items:
> - enum:
> - qcom,qcm2290-smmu-500
> + - qcom,qdu1000-smmu-500
> + - qcom,qru1000-smmu-500
No. You sent entirely different DTS.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-10-15 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 22:10 [PATCH v2 0/2] Add smmu support for QDU1000/QRU1000 SoCs Melody Olvera
2022-10-14 22:10 ` [PATCH v2 1/2] dt-bindings: arm-smmu: Add compatible bindings for QDU1000 and QRU1000 Melody Olvera
2022-10-15 15:16 ` Krzysztof Kozlowski [this message]
2022-10-14 22:10 ` [PATCH v2 2/2] drivers: arm-smmu-impl: Add QDU1000 and QRU1000 iommu implementation Melody Olvera
2022-10-14 23:55 ` [PATCH v2 0/2] Add smmu support for QDU1000/QRU1000 SoCs Melody Olvera
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=fd36ae9b-2f15-43a1-51dd-bed475f12e5b@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_molvera@quicinc.com \
--cc=robh+dt@kernel.org \
--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).