From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 4/4] nvme: split pci module out of core module
Date: Wed, 10 Feb 2016 15:12:53 +0000 [thread overview]
Message-ID: <20160210151253.GB32064@localhost.localdomain> (raw)
In-Reply-To: <1454970284-29543-5-git-send-email-mlin@kernel.org>
On Mon, Feb 08, 2016@02:24:44PM -0800, Ming Lin wrote:
> This splits nvme.ko into 2 modules:
> nvme-core.ko: the core part
> nvme.ko: the PCI driver
Do we want to let PCI take the generic "nvme.ko" name? What will the
other nvme transport modules be called?
Otherwise, looks good to me.
next prev parent reply other threads:[~2016-02-10 15:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:24 [PATCH 0/4] nvme: split pci module out of core module Ming Lin
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 [this message]
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=20160210151253.GB32064@localhost.localdomain \
--to=keith.busch@intel.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 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).