mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Peter <sven@kernel.org>
To: j@jannau.net, Alyssa Rosenzweig <alyssa@rosenzweig.io>,
	Neal Gompa <neal@gompa.dev>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Mark Kettenis <kettenis@openbsd.org>,
	Hector Martin <marcan@marcan.st>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Apple device tree sync from downstream kernel
Date: Sat, 16 Aug 2025 16:06:37 +0200	[thread overview]
Message-ID: <b7491aed-8942-4dd0-b2c8-349a9db1ca39@kernel.org> (raw)
In-Reply-To: <20250813-apple-dt-sync-6-17-v1-0-209f15d10aa0@jannau.net>

On 13.08.25 11:53, Janne Grunau via B4 Relay wrote:
> This series pulls changes from the downstream device trees which are
> supported in upstream kernel.
> Most importantly it fixes the PCIe description for a specific iMac model
> (iMac M1, 2 USB-C ports, 2021). This is worked around in the downstream
> kernel by not disabling the port. In preparation for submitting M2
> Pro/Max/Ultra devices trees I investigated the issue on the similarly
> affected M2 Pro Mac mini and fixed it this way.
> It completes the Wlan/BT device nodes for t600x based devices and adds
> the missing 15-inch Macbook Air (M2, 2023).
> 
> Checkpatch emits following warnings:
> 
> WARNING: DT compatible string vendor "pci14e4" appears un-documented --
> check ./Documentation/devicetree/bindings/vendor-prefixes.yaml
> 
> Which I chose to ignore. `vendor-prefixes.yaml` prefixes contains no
> other mapping for PCI vendor code and the list of ignored prefixes
> forbids extending it. Both options feel wrong though. "pci${vendor}" is
> clearly a vendor prefix but duplicating the PCI vendor data base feels
> wrong. `vendor-prefixes.yaml` currently does not contain and PCI vendor
> aliases.
> 
> Signed-off-by: Janne Grunau <j@jannau.net>
> ---

For the entire series:

Reviewed-by: Sven Peter <sven@kernel.org>



Thanks,


Sven


  parent reply	other threads:[~2025-08-16 14:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13  9:53 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
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 ` Sven Peter [this message]
2025-08-19 18:38 ` [PATCH 0/5] Apple device tree sync from downstream kernel 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=b7491aed-8942-4dd0-b2c8-349a9db1ca39@kernel.org \
    --to=sven@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=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

all inboxes | Powered by JetHome®