From: Will Deacon <will@kernel.org>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>, joro@8bytes.org
Cc: catalin.marinas@arm.com, mark.rutland@arm.com,
kernel-team@android.com, Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] dt-bindings: arm-smmu: Document Adreno SMMU for Nord SoC
Date: Wed, 7 Oct 2026 10:01:23 +0100 [thread overview]
Message-ID: <asYKYzDvNBLjnotz@willie-the-truck> (raw)
In-Reply-To: <asW7Lay9i_hiuTcP@QCOM-aGQu4IUr3Y>
On Wed, Oct 07, 2026 at 11:23:25AM +0800, Shawn Guo wrote:
> On Fri, Oct 02, 2026 at 05:46:40PM +0100, Will Deacon wrote:
> > On Wed, 02 Sep 2026 09:38:58 +0800, Shawn Guo wrote:
> > > Add specific compatible string to document the GPU SMMU present on
> > > Nord SoC, and constrain it to the single HLOS vote clock.
> > >
> > >
> >
> > Applied to iommu (arm/smmu/bindings), thanks!
> >
> > [1/1] dt-bindings: arm-smmu: Document Adreno SMMU for Nord SoC
> > https://git.kernel.org/iommu/c/e9da5ec4a1d6
>
> Hi Will,
>
> Could we get this into linux-next please?
I'm hoping Joerg can rebuild the 'next' branch soon, but it's LPC this
week so I know that everybody is busy.
Will
prev parent reply other threads:[~2026-10-07 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 1:38 [PATCH v2] dt-bindings: arm-smmu: Document Adreno SMMU for Nord SoC Shawn Guo
2026-09-08 7:20 ` Krzysztof Kozlowski
2026-09-08 7:32 ` Bartosz Golaszewski
2026-09-28 11:20 ` Shawn Guo
2026-09-29 11:41 ` Will Deacon
2026-10-02 16:46 ` Will Deacon
2026-10-07 3:23 ` Shawn Guo
2026-10-07 9:01 ` Will Deacon [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=asYKYzDvNBLjnotz@willie-the-truck \
--to=will@kernel.org \
--cc=bibek.patro@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=shengchao.guo@oss.qualcomm.com \
/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