From: Richard Acayan <mailingradian@gmail.com>
To: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 0/1] iommu: SMMU for SDM670
Date: Mon, 7 Nov 2022 22:02:44 -0500 [thread overview]
Message-ID: <Y2nG1ExgpYVm2sY+@mailingradian> (raw)
In-Reply-To: <20221108025847.58352-1-mailingradian@gmail.com>
On Mon, Nov 07, 2022 at 09:58:48PM -0500, Richard Acayan wrote:
> Changes since v3:
> - drop driver patch
This is v4. I forgot to increment the version in the subject header. My
apologies.
>
> Changes since v2:
> - rewrite driver patch (2/2)
> - rebase on (1/2):
> https://lore.kernel.org/linux-iommu/20221102184420.534094-1-dmitry.baryshkov@linaro.org/
> - reset review process (1-2/2)
>
> Changes since v1 (no emails related to this series since last week):
> - accumulate tags (both were added because it seems like the discussion
> ended in agreement to keep adding compatible strings to the driver)
>
> This adds the compatible string for the Qualcomm Snapdragon 670's SMMU. The
> SMMU is necessary for GENI I2C, included in initial bringup because it
> doesn't need non-trivial patches except for patches conventionally added
> before the initial device tree (global clock controller and pinctrl).
>
> Richard Acayan (1):
> dt-bindings: iommu: arm-smmu: add sdm670 compatible
>
> Documentation/devicetree/bindings/iommu/arm,smmu.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> --
> 2.38.1
>
prev parent reply other threads:[~2022-11-08 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 2:58 [PATCH v3 0/1] iommu: SMMU for SDM670 Richard Acayan
2022-11-08 2:58 ` [PATCH v3 1/1] dt-bindings: iommu: arm-smmu: add sdm670 compatible Richard Acayan
2022-11-08 3:02 ` Richard Acayan [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=Y2nG1ExgpYVm2sY+@mailingradian \
--to=mailingradian@gmail.com \
--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-arm-msm@vger.kernel.org \
--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).