All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Arnd Bergmann <arnd@arndb.de>,
	Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Jay Freyensee <james_p_freyensee@linux.intel.com>,
	Ming Lin <ming.l@ssi.samsung.com>,
	Jay Sternberg <jay.e.sternberg@intel.com>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme: add back dependency on CONFIG_BLOCK
Date: Tue, 6 Sep 2016 16:09:26 +0300	[thread overview]
Message-ID: <d7099c1b-730f-1617-f683-2447bedd3e6d@grimberg.me> (raw)
In-Reply-To: <20160906125827.1595094-1-arnd@arndb.de>


> A recent change removed the dependency on BLK_DEV_NVME, which implies
> the dependency on PCI and BLOCK. We don't need CONFIG_PCI, but without
> CONFIG_BLOCK we get tons of build errors, e.g.

Thanks Arnd, queued for the next round of rc fixes.

With a slight modification to the component in the subject line
(nvme-rdma).

WARNING: multiple messages have this Message-ID (diff)
From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH] nvme: add back dependency on CONFIG_BLOCK
Date: Tue, 6 Sep 2016 16:09:26 +0300	[thread overview]
Message-ID: <d7099c1b-730f-1617-f683-2447bedd3e6d@grimberg.me> (raw)
In-Reply-To: <20160906125827.1595094-1-arnd@arndb.de>


> A recent change removed the dependency on BLK_DEV_NVME, which implies
> the dependency on PCI and BLOCK. We don't need CONFIG_PCI, but without
> CONFIG_BLOCK we get tons of build errors, e.g.

Thanks Arnd, queued for the next round of rc fixes.

With a slight modification to the component in the subject line
(nvme-rdma).

  reply	other threads:[~2016-09-06 13:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 12:58 [PATCH] nvme: add back dependency on CONFIG_BLOCK Arnd Bergmann
2016-09-06 12:58 ` Arnd Bergmann
2016-09-06 13:09 ` Sagi Grimberg [this message]
2016-09-06 13:09   ` Sagi Grimberg
2016-09-06 13:36   ` Christoph Hellwig
2016-09-06 13:36     ` 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=d7099c1b-730f-1617-f683-2447bedd3e6d@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=arnd@arndb.de \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=james_p_freyensee@linux.intel.com \
    --cc=jay.e.sternberg@intel.com \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.l@ssi.samsung.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 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.