From: axboe@fb.com (Jens Axboe)
Subject: NVMe driver split for Linux 4.5
Date: Tue, 1 Dec 2015 11:01:20 -0700 [thread overview]
Message-ID: <565DE070.7000000@fb.com> (raw)
In-Reply-To: <1448872593-4096-1-git-send-email-hch@lst.de>
On 11/30/2015 01:36 AM, Christoph Hellwig wrote:
> This series contains a the split of the NVMe driver into a common core part
> and a PCIe specific fontend.
> nvme driver split to show how I want to get started.
>
> To make testing easier I've pushed out a git tree with this and all
> dependencies:
>
> git://git.infradead.org/users/hch/block.git nvme-split.6
>
> or in gitweb:
>
> https://urldefense.proofpoint.com/v2/url?u=http-3A__git.infradead.org_users_hch_block.git_shortlog_refs_heads_nvme-2Dsplit.6&d=CwIBAg&c=5VD0RTtNlTh3ycd41b3MUw&r=cK1a7KivzZRh1fKQMjSm2A&m=CHSSJfe8EfWpVJ_bCvWDDBlIAgwYVoXEPiF3tz_LeTY&s=x1qUJfAkEfzsYRtJchSLNoGBLTUdxeve1OOrHlVQuWM&e=
>
> Chances since the previous post from the patchbomb:
> - use vendor ID from Identify data in the SCSI translation layer
> - add common enable/shutdown code from the NVMe loop series
I've added this series for 4.5, it's in the for-4.5/nvme branch.
--
Jens Axboe
prev parent reply other threads:[~2015-12-01 18:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 8:36 NVMe driver split for Linux 4.5 Christoph Hellwig
2015-11-30 8:36 ` [PATCH 01/23] blk-mq: add a flags parameter to blk_mq_alloc_request Christoph Hellwig
2015-11-30 8:36 ` [PATCH 02/23] nvme: move struct nvme_iod to pci.c Christoph Hellwig
2015-11-30 8:36 ` [PATCH 03/23] nvme: split command submission helpers out of pci.c Christoph Hellwig
2015-11-30 8:36 ` [PATCH 04/23] nvme: use offset instead of a struct for registers Christoph Hellwig
2015-11-30 8:36 ` [PATCH 05/23] nvme: split nvme_trans_device_id_page Christoph Hellwig
2015-11-30 8:36 ` [PATCH 06/23] nvme: use vendor it from identify Christoph Hellwig
2015-11-30 8:36 ` [PATCH 07/23] nvme: split a new struct nvme_ctrl out of struct nvme_dev Christoph Hellwig
2015-11-30 8:36 ` [PATCH 08/23] nvme: simplify nvme_setup_prps calling convention Christoph Hellwig
2015-11-30 8:36 ` [PATCH 09/23] nvme: refactor nvme_queue_rq Christoph Hellwig
2015-11-30 8:36 ` [PATCH 10/23] nvme: factor out a nvme_unmap_data helper Christoph Hellwig
2015-11-30 8:36 ` [PATCH 11/23] nvme: move nvme_error_status to common code Christoph Hellwig
2015-11-30 8:36 ` [PATCH 12/23] nvme: move nvme_setup_flush and nvme_setup_rw " Christoph Hellwig
2015-11-30 8:36 ` [PATCH 13/23] nvme: split __nvme_submit_sync_cmd Christoph Hellwig
2015-11-30 8:36 ` [PATCH 14/23] nvme: use the block layer for userspace passthrough metadata Christoph Hellwig
2015-11-30 8:36 ` [PATCH 15/23] nvme: move block_device_operations and ns/ctrl freeing to common code Christoph Hellwig
2015-11-30 8:36 ` [PATCH 16/23] nvme: add explicit quirk handling Christoph Hellwig
2015-12-01 18:01 ` Jens Axboe [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=565DE070.7000000@fb.com \
--to=axboe@fb.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.