From: Conor Dooley <conor@kernel.org>
To: Joel Stanley <joel@jms.id.au>
Cc: Paul Walmsley <pjw@kernel.org>, Rob Herring <robh@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Anup Patel <anup@brainfault.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Nicholas Piggin <npiggin@gmail.com>,
Michael Ellerman <mpe@kernel.org>,
Drew Fustini <fustini@kernel.org>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: aplic: Add Tenstorrent Atlantis compatible
Date: Wed, 3 Jun 2026 17:19:10 +0100 [thread overview]
Message-ID: <20260603-landed-starting-e9ae05ee5bad@spud> (raw)
In-Reply-To: <20260603074222.593243-2-joel@jms.id.au>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Wed, Jun 03, 2026 at 05:12:13PM +0930, Joel Stanley wrote:
> Add compatible for APLIC in Tenstorrent Atlantis SoC.
>
> Signed-off-by: Drew Fustini <fustini@kernel.org>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
And here. The contents all look fine of course.
pw-bot: changes-requested
> ---
> .../devicetree/bindings/interrupt-controller/riscv,aplic.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml b/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml
> index 0718071444d2..d4e17861eda4 100644
> --- a/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml
> +++ b/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml
> @@ -29,6 +29,7 @@ properties:
> - enum:
> - qemu,aplic
> - spacemit,k3-aplic
> + - tenstorrent,atlantis-aplic
> - const: riscv,aplic
>
> reg:
> --
> 2.47.3
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-06-03 16:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 7:42 [PATCH 0/7] riscv: dts: tenstorrent: Add Atlantis platform Joel Stanley
2026-06-03 7:42 ` [PATCH 1/7] dt-bindings: aplic: Add Tenstorrent Atlantis compatible Joel Stanley
2026-06-03 7:47 ` Anup Patel
2026-06-03 16:19 ` Conor Dooley [this message]
2026-06-03 7:42 ` [PATCH 2/7] dt-bindings: imsics: " Joel Stanley
2026-06-03 7:48 ` Anup Patel
2026-06-03 16:18 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 3/7] dt-bindings: riscv: cpus: Add Tenstorrent Ascalon Joel Stanley
2026-06-03 16:18 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 4/7] dt-bindings: timer: Add RISC-V ACLINT bindings Joel Stanley
2026-06-03 7:50 ` Anup Patel
2026-06-03 7:55 ` sashiko-bot
2026-06-03 9:23 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 5/7] dt-bindings: riscv: add Smrnmi extension description Joel Stanley
2026-06-03 16:17 ` Conor Dooley
2026-06-03 7:42 ` [PATCH 6/7] dt-bindings: riscv: Add Tenstorrent Atlantis platform Joel Stanley
2026-06-03 16:17 ` Conor Dooley
2026-06-03 19:37 ` Drew Fustini
2026-06-03 7:42 ` [PATCH 7/7] riscv: dts: tenstorrent: Add " Joel Stanley
2026-06-03 8:04 ` sashiko-bot
2026-06-03 9:16 ` Conor Dooley
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=20260603-landed-starting-e9ae05ee5bad@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=joel@jms.id.au \
--cc=linux-riscv@lists.infradead.org \
--cc=mpe@kernel.org \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@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