From: mlin@kernel.org (Ming Lin)
Subject: [PATCH 4/4] nvme: split pci module out of core module
Date: Tue, 09 Feb 2016 10:26:45 -0800 [thread overview]
Message-ID: <1455042405.8832.4.camel@ssi> (raw)
In-Reply-To: <20160209085656.GJ27969@c203.arch.suse.de>
On Tue, 2016-02-09@09:56 +0100, Johannes Thumshirn wrote:
> 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
> >
> > Also changes config name:
> > s/CONFIG_BLK_DEV_NVME/CONFIG_NVME_PCI
> > s/CONFIG_BLK_DEV_NVME_SCSI/CONFIG_NVME_SCSI
>
> Is there any auto-migration for those who already have CONFIG_BLK_DEV_NVME set
> in their kernel configs? If not, this could lead to a bunch of non-booting
> systems.
Hi Michal(CCed),
As you saw above, I'm changing:
CONFIG_BLK_DEV_NVME to CONFIG_NVME_PCI
and
CONFIG_BLK_DEV_NVME_SCSI to CONFIG_NVME_SCSI
Is there Kconfig magic to keep existing config working?
ie, if CONFIG_BLK_DEV_NVME was set in .config, then CONFIG_NVME_PCI
should be set automatically?
Thanks,
Ming
next prev parent reply other threads:[~2016-02-09 18:26 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 [this message]
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=1455042405.8832.4.camel@ssi \
--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 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.