From: Sagi Grimberg <sagi@grimberg.me>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-nvme@lists.infradead.org
Cc: Jens Axboe <axboe@fb.com>, Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org, Paul Pawlowski <paul@mrarm.io>
Subject: Re: [PATCH v4 0/4] nvme-pci: Support for Apple 201+ (T2 chip)
Date: Thu, 8 Aug 2019 16:52:05 -0700 [thread overview]
Message-ID: <ae14ef26-b4a5-1ef2-e2a9-581e813893fe@grimberg.me> (raw)
In-Reply-To: <20190807075122.6247-1-benh@kernel.crashing.org>
> This series combines the original series and an updated version of the
> shared tags patch, and is rebased on nvme-5.4.
>
> This adds support for the controller found in recent Apple machines
> which is basically a SW emulated NVME controller in the T2 chip.
>
> The original reverse engineering work was done by
> Paul Pawlowski <paul@mrarm.io>.
Thanks, pulled to nvme-5.4
prev parent reply other threads:[~2019-08-08 23:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 7:51 [PATCH v4 0/4] nvme-pci: Support for Apple 201+ (T2 chip) Benjamin Herrenschmidt
2019-08-07 7:51 ` [PATCH v4 1/4] nvme-pci: Pass the queue to SQ_SIZE/CQ_SIZE macros Benjamin Herrenschmidt
2019-08-07 7:51 ` [PATCH v4 2/4] nvme-pci: Add support for variable IO SQ element size Benjamin Herrenschmidt
2019-08-22 0:28 ` Christoph Hellwig
2019-08-22 0:31 ` Benjamin Herrenschmidt
2019-08-22 18:02 ` Sagi Grimberg
2019-08-23 0:41 ` Benjamin Herrenschmidt
2019-08-23 2:52 ` Sagi Grimberg
2019-08-23 3:50 ` Benjamin Herrenschmidt
2019-08-07 7:51 ` [PATCH v4 3/4] nvme-pci: Add support for Apple 2018+ models Benjamin Herrenschmidt
2019-08-22 0:28 ` Christoph Hellwig
2019-08-07 7:51 ` [PATCH v4 4/4] nvme-pci: Support shared tags across queues for Apple 2018 controllers Benjamin Herrenschmidt
2019-08-22 0:29 ` Christoph Hellwig
2019-08-08 23:52 ` Sagi Grimberg [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=ae14ef26-b4a5-1ef2-e2a9-581e813893fe@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@fb.com \
--cc=benh@kernel.crashing.org \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=paul@mrarm.io \
/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;
as well as URLs for NNTP newsgroup(s).