From: Janne Grunau <j@jannau.net>
To: Rob Herring <robh@kernel.org>
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 2/5] arm64: dts: apple: t600x: Comple WiFi properties
Date: Thu, 21 Aug 2025 12:29:47 +0200 [thread overview]
Message-ID: <20250821102947.GC1270980@robin.jannau.net> (raw)
In-Reply-To: <20250820190920.GB538860-robh@kernel.org>
On Wed, Aug 20, 2025 at 02:09:20PM -0500, Rob Herring wrote:
> On Wed, Aug 13, 2025 at 11:53:34AM +0200, Janne Grunau wrote:
> > From: Hector Martin <marcan@marcan.st>
>
> What does 'Comple' in the subject mean?
'Complete'. I've changed it locally to
"arm64: dts: apple: t600x: Add missing WiFi properties" and removed
stray words from the end of the commit message.
Janne
next prev parent reply other threads:[~2025-08-21 10:29 UTC|newest]
Thread overview: 12+ 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 ` [PATCH 1/5] arm64: dts: apple: t8103-j457: Fix PCIe ethernet iommu-map Janne Grunau via B4 Relay
2025-08-13 9:53 ` [PATCH 2/5] arm64: dts: apple: t600x: Comple WiFi properties Janne Grunau via B4 Relay
2025-08-20 19:09 ` Rob Herring
2025-08-21 10:29 ` Janne Grunau [this message]
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 ` [PATCH 4/5] dt-bindings: arm: apple: Add t8112 j415 compatible Janne Grunau via B4 Relay
2025-08-20 19:07 ` Rob Herring
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-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=20250821102947.GC1270980@robin.jannau.net \
--to=j@jannau.net \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®