From: mlin@kernel.org (Ming Lin)
Subject: [PATCH 0/4] nvme: split pci module out of core module
Date: Mon, 8 Feb 2016 14:24:40 -0800 [thread overview]
Message-ID: <1454970284-29543-1-git-send-email-mlin@kernel.org> (raw)
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
Ming Lin (4):
nvme: move timeout variables to core.c and export it
nvme: export more symbols
nvme: split dev_list_lock
nvme: split pci module out of core module
drivers/nvme/host/Kconfig | 10 +++++++---
drivers/nvme/host/Makefile | 10 ++++++----
drivers/nvme/host/core.c | 40 +++++++++++++++++++++++++++++++++++++---
drivers/nvme/host/nvme.h | 2 --
drivers/nvme/host/pci.c | 26 ++------------------------
5 files changed, 52 insertions(+), 36 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-08 22:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:24 Ming Lin [this message]
2016-02-08 22:24 ` [PATCH 1/4] nvme: move timeout variables to core.c and export it Ming Lin
2016-02-09 9:25 ` Christoph Hellwig
2016-02-09 12:43 ` Johannes Thumshirn
2016-02-09 12:46 ` Matias Bjørling
2016-02-08 22:24 ` [PATCH 2/4] nvme: export more symbols Ming Lin
2016-02-09 9:25 ` Christoph Hellwig
2016-02-09 12:42 ` Johannes Thumshirn
2016-02-09 12:56 ` Matias Bjørling
2016-02-09 13:07 ` Christoph Hellwig
2016-02-08 22:24 ` [PATCH 3/4] nvme: split dev_list_lock Ming Lin
2016-02-09 9:26 ` Christoph Hellwig
2016-02-09 12:41 ` Johannes Thumshirn
2016-02-09 13:14 ` Christoph Hellwig
2016-02-09 13:34 ` Johannes Thumshirn
2016-02-08 22:24 ` [PATCH 4/4] nvme: split pci module out of core module Ming Lin
2016-02-09 8:56 ` Johannes Thumshirn
2016-02-09 18:26 ` Ming Lin
2016-02-10 13:35 ` Michal Marek
2016-02-09 9:26 ` Christoph Hellwig
2016-02-10 0:09 ` Ming Lin
2016-02-10 15:12 ` Keith Busch
2016-02-10 15:31 ` Ming Lin
2016-02-09 9:24 ` [PATCH 0/4] " Christoph Hellwig
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=1454970284-29543-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).