Have you reported this upstream?

It does look to me that this dependency is working the wrong way, that
CONFIG_BLK_DEV_NVME depends on CONFIG_NVME and not the other way around.
The driver enabled by CONFIG_BLK_DEV_NVME has no entry points other than
the struct pci_driver callbacks, but it does call into the code enabled
by CONFIG_NVME.

I'm not convinced that yours is the correct fix though. I suspect that
BLK_DEV_NVME should have a "depends on NVM" or "select NVM" instead.
What I will do though is revert 32c662c58a9b9d0c99e713a14ca323a9a91c73a0
and change BLK_DEV_NVME back to =m. You should probably follow up
upstream to get a fix in place there.

** Changed in: linux (Ubuntu Bionic)
       Status: Triaged => In Progress

** Changed in: linux (Ubuntu Bionic)
     Assignee: (unassigned) => Seth Forshee (sforshee)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759893

Title:
  [18.04][config] regression: nvme and nvme_core couldn't be built as
  modules starting 4.15-rc2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759893/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to