From: Rob Herring <robh@kernel.org>
To: Janne Grunau <j@jannau.net>
Cc: Sven Peter <sven@kernel.org>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
Neal Gompa <neal@gompa.dev>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mark Kettenis <kettenis@openbsd.org>,
Hector Martin <marcan@marcan.st>,
asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] dt-bindings: arm: apple: Add t8112 j415 compatible
Date: Wed, 20 Aug 2025 14:07:08 -0500 [thread overview]
Message-ID: <20250820190708.GA538860-robh@kernel.org> (raw)
In-Reply-To: <20250813-apple-dt-sync-6-17-v1-4-209f15d10aa0@jannau.net>
On Wed, Aug 13, 2025 at 11:53:36AM +0200, Janne Grunau wrote:
> This adds the "apple,j415" (MacBook Air (15-inch, M2, 2023) to the
> apple,t8112 platform.
>
> Signed-off-by: Janne Grunau <j@jannau.net>
> ---
> Documentation/devicetree/bindings/arm/apple.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/apple.yaml b/Documentation/devicetree/bindings/arm/apple.yaml
> index da60e9de1cfbd0151e973c3aafba6d0880fc21aa..3b90b5df60507b245de387de104a4e64f234139a 100644
> --- a/Documentation/devicetree/bindings/arm/apple.yaml
> +++ b/Documentation/devicetree/bindings/arm/apple.yaml
> @@ -93,6 +93,7 @@ description: |
>
> - MacBook Air (M2, 2022)
> - MacBook Pro (13-inch, M2, 2022)
> + - MacBook Pro (15-inch, M2, 2023)
s/Pro/Air/?
> - Mac mini (M2, 2023)
>
> And devices based on the "M1 Pro", "M1 Max" and "M1 Ultra" SoCs:
> @@ -279,6 +280,7 @@ properties:
> items:
> - enum:
> - apple,j413 # MacBook Air (M2, 2022)
> + - apple,j415 # MacBook Air (M2, 2023)
> - apple,j473 # Mac mini (M2, 2023)
> - apple,j493 # MacBook Pro (13-inch, M2, 2022)
> - const: apple,t8112
>
> --
> 2.50.1
>
next prev parent reply other threads:[~2025-08-20 19:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 9:53 [PATCH 0/5] Apple device tree sync from downstream kernel Janne Grunau via B4 Relay
2025-08-13 9:53 ` Janne Grunau
2025-08-13 9:53 ` [PATCH 1/5] arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map Janne Grunau via B4 Relay
2025-08-13 9:53 ` Janne Grunau
2025-08-13 9:53 ` [PATCH 2/5] arm64: dts: apple: t600x: Comple WiFi properties Janne Grunau via B4 Relay
2025-08-13 9:53 ` Janne Grunau
2025-08-20 19:09 ` Rob Herring
2025-08-21 10:29 ` Janne Grunau
2025-08-13 9:53 ` [PATCH 3/5] arm64: dts: apple: t600x: Add bluetooth device nodes Janne Grunau via B4 Relay
2025-08-13 9:53 ` Janne Grunau
2025-08-13 9:53 ` [PATCH 4/5] dt-bindings: arm: apple: Add t8112 j415 compatible Janne Grunau via B4 Relay
2025-08-13 9:53 ` Janne Grunau
2025-08-20 19:07 ` Rob Herring [this message]
2025-08-21 10:31 ` Janne Grunau
2025-08-13 9:53 ` [PATCH 5/5] arm64: dts: apple: Add devicetreee for t8112-j415 Janne Grunau via B4 Relay
2025-08-13 9:53 ` Janne Grunau
2025-08-16 14:06 ` [PATCH 0/5] Apple device tree sync from downstream kernel Sven Peter
2025-08-19 18:38 ` Neal Gompa
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=20250820190708.GA538860-robh@kernel.org \
--to=robh@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=j@jannau.net \
--cc=kettenis@openbsd.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcan@marcan.st \
--cc=neal@gompa.dev \
--cc=sven@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.