Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 22 Mar 2022 17:26:45 +0000
From:   Alyssa Rosenzweig <alyssa@rosenzweig.io>
To:     Sven Peter <sven@svenpeter.dev>
Cc:     Hector Martin <marcan@marcan.st>, Rob Herring <robh+dt@kernel.org>,
        Arnd Bergmann <arnd@arndb.de>, Keith Busch <kbusch@kernel.org>,
        Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
        Sagi Grimberg <sagi@grimberg.me>,
        Marc Zyngier <maz@kernel.org>, devicetree@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
        linux-nvme@lists.infradead.org
Subject: Re: [PATCH 0/9] Apple M1 (Pro/Max) NVMe driver
Message-ID: <YjoG1UqPhJaKbTPX@rosenzweig.io>
References: <20220321165049.35985-1-sven@svenpeter.dev>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220321165049.35985-1-sven@svenpeter.dev>
Precedence: bulk

> The driver itself has been successfully used by multiple people as
> their daily driver for weeks at this point and no major issues have
> been reported.

FWIW, various versions of your NVMe code have been my daily driver for
development since late 2021 now, along with the display driver based on
your RTKit library here. I'm not qualified to judge code quality or
fitness for mainline, but I can testify that it's functional.

(Not a formal T-b since I haven't tested this exact version of the patch
series, though.)