From: Nick Chan <towinchenmi@gmail.com>
To: Sven Peter <sven@kernel.org>, Janne Grunau <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>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v4 0/4] Add support ANS2 NVMe on Apple A11
Date: Mon, 25 Aug 2025 17:24:31 +0800 [thread overview]
Message-ID: <89826428-4a54-435b-b564-b0be49b8c7bc@gmail.com> (raw)
In-Reply-To: <20250825-t8015-nvme-v4-0-6ffc8f891b6e@gmail.com>
On 25/8/2025 17:15, Nick Chan wrote:
[...]
> Patch 6-7 adds support for the NVMe controller found in Apple A11 SoC> Patch 8-9 adds the required device tree nodes.
A correction since patches are removed:
Patch 1-2 adds support for the NVMe controller found in Apple A11 SoC
Patch 3-4 adds the required device tree nodes.
>
> Signed-off-by: Nick Chan <towinchenmi@gmail.com>
> ---
> Changes in v4:
> - Remove the remaining added long line in drivers/nvme/host/apple.c
> - Drop already applied SART and mailbox patches (based on top of
> apple-soc/drivers-6.18)
> - Link to v3: https://lore.kernel.org/r/20250821-t8015-nvme-v3-0-14a4178adf68@gmail.com
[...]
prev parent reply other threads:[~2025-08-25 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 9:15 Nick Chan
2025-08-25 9:15 ` [PATCH v4 1/4] dt-bindings: nvme: apple,nvme-ans: Add " Nick Chan
2025-08-25 22:13 ` Rob Herring
2025-08-25 9:15 ` [PATCH v4 2/4] nvme: apple: Add Apple A11 support Nick Chan
2025-08-25 9:15 ` [PATCH v4 3/4] arm64: dts: apple: t8015: Fix PCIE power domains dependencies Nick Chan
2025-08-25 9:15 ` [PATCH v4 4/4] arm64: dts: apple: t8015: Add NVMe nodes Nick Chan
2025-08-25 9:24 ` Nick Chan [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=89826428-4a54-435b-b564-b0be49b8c7bc@gmail.com \
--to=towinchenmi@gmail.com \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=axboe@kernel.dk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hch@lst.de \
--cc=j@jannau.net \
--cc=kbusch@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=neal@gompa.dev \
--cc=robh@kernel.org \
--cc=sagi@grimberg.me \
--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®