From: mlin@kernel.org (Ming Lin)
Subject: [PATCH v2 0/5] split pci module out of core module
Date: Tue, 9 Feb 2016 16:07:48 -0800 [thread overview]
Message-ID: <1455062873-18392-1-git-send-email-mlin@kernel.org> (raw)
From: Ming Lin <ming.l@ssi.samsung.com>
We'll have nvme over fabric dirver soon.
This series split nvme pci module out of nvme core module.
nvme.ko is split into 2 modules:
nvme-core.ko: the core part
nvme.ko: the PCI driver
v2:
- add Sagi's patch to take proper references to the transport driver on open
- add review tags
- don't change the CONFIG name
Ming Lin (4):
nvme: move timeout variables to core.c and export it
nvme: export more functions
nvme: split dev_list_lock
nvme: split pci module out of core module
Sagi Grimberg (1):
nvme/host: reference the fabric module for each bdev open callout
drivers/nvme/host/Kconfig | 6 ++++-
drivers/nvme/host/Makefile | 10 ++++----
drivers/nvme/host/core.c | 57 ++++++++++++++++++++++++++++++++++++++++++----
drivers/nvme/host/nvme.h | 3 +--
drivers/nvme/host/pci.c | 27 +++-------------------
5 files changed, 67 insertions(+), 36 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-10 0:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 0:07 Ming Lin [this message]
2016-02-10 0:07 ` [PATCH v2 1/5] nvme/host: reference the fabric module for each bdev open callout Ming Lin
2016-02-10 9:18 ` Johannes Thumshirn
2016-02-10 0:07 ` [PATCH v2 2/5] nvme: move timeout variables to core.c and export it Ming Lin
2016-02-10 10:37 ` Sagi Grimberg
2016-02-10 0:07 ` [PATCH v2 3/5] nvme: export more functions Ming Lin
2016-02-10 10:37 ` Sagi Grimberg
2016-02-10 0:07 ` [PATCH v2 4/5] nvme: split dev_list_lock Ming Lin
2016-02-10 10:38 ` Sagi Grimberg
2016-02-10 0:07 ` [PATCH v2 5/5] nvme: split pci module out of core module Ming Lin
2016-02-10 10:38 ` Sagi Grimberg
2016-02-10 10:38 ` Sagi Grimberg
2016-02-10 8:21 ` [PATCH v2 0/5] " Christoph Hellwig
2016-02-10 15:37 ` Ming Lin
2016-02-10 16:11 ` Christoph Hellwig
2016-02-10 16:20 ` Ming Lin
2016-02-10 16:22 ` Christoph Hellwig
2016-02-10 17:29 ` Ming Lin
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=1455062873-18392-1-git-send-email-mlin@kernel.org \
--to=mlin@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;
as well as URLs for NNTP newsgroup(s).