From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] NVMe: Add explicit block config dependency
Date: Mon, 12 Oct 2015 19:42:46 +0200 [thread overview]
Message-ID: <20151012174246.GA30222@lst.de> (raw)
In-Reply-To: <1444671458-9947-1-git-send-email-keith.busch@intel.com>
On Mon, Oct 12, 2015@11:37:38AM -0600, Keith Busch wrote:
> The nvme driver was moved from drivers/block, losing our implicit
> dependency on CONFIG_BLOCK. This makes it an explicit driver dependency.
>
> Reported-by: Jim Davis <jim.epost at gmail.com>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
Oh, that explains the odd errors - I actually just got a similar one
from the buildbot and couldn't make sense of it.
Looks good,
Reviewed-by: Christoph Hellwig <hch at lst.de>
prev parent reply other threads:[~2015-10-12 17:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 17:37 [PATCH] NVMe: Add explicit block config dependency Keith Busch
2015-10-12 17:42 ` Christoph Hellwig [this message]
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=20151012174246.GA30222@lst.de \
--to=hch@lst.de \
/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.