linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@fb.com>
To: Arnd Bergmann <arnd@arndb.de>, Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Sagi Grimberg <sagi@grimberg.me>,
	<linux-nvme@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvme-loop: add configfs dependency
Date: Tue, 12 Jul 2016 08:36:57 -0700	[thread overview]
Message-ID: <57850E99.1080901@fb.com> (raw)
In-Reply-To: <12070715.hig6uZ5icx@wuerfel>

On 07/11/2016 01:29 PM, Arnd Bergmann wrote:
> On Sunday, July 10, 2016 2:14:17 PM CEST Christoph Hellwig wrote:
>> On Thu, Jul 07, 2016 at 08:35:17AM -0600, Jens Axboe wrote:
>>> Thanks Arnd, applied.
>>
>> Actually I think we should replace the select with the depends.  In
>> fact I though I had done that a while ago, but I must have messed it up.
>
> Makes sense. I ran into the same problem on NVME_TARGET_RDMA now,
> which otherwise needs dependencies on both CONFIG_BLOCK and
> CONFIGFS_FS:
>
>      warning: (NVME_TARGET_LOOP && NVME_TARGET_RDMA) selects NVME_TARGET which has unmet direct dependencies (BLOCK && CONFIGFS_FS)
>      0xA002B368 Mon Jul 11 18:00:45 CEST 2016 failed
>      In file included from ../drivers/nvme/target/core.c:16:0:
>      drivers/nvme/target/nvmet.h:222:14: error: field 'inline_bio' has incomplete type
>        struct bio  inline_bio;
>                    ^~~~~~~~~~
>      drivers/nvme/target/core.c: In function 'nvmet_async_event_work':
>      drivers/nvme/target/core.c:98:3: error: implicit declaration of function 'kfree' [-Werror=implicit-function-declaration]
>         kfree(aen);
>         ^~~~~
>      ../drivers/nvme/target/core.c: In function 'nvmet_ns_enable':
>      ../drivers/nvme/target/core.c:269:13: error: implicit declaration of function 'blkdev_get_by_path' [-Werror=implicit-function-declaration]
>        ns->bdev = blkdev_get_by_path(ns->device_path, FMODE_READ | FMODE_WRITE,
>
> Folding in my patch below should address that too.

I folded this in.

-- 
Jens Axboe

  reply	other threads:[~2016-07-12 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  9:01 [PATCH] nvme-loop: add configfs dependency Arnd Bergmann
2016-07-07 14:35 ` Jens Axboe
2016-07-10 12:14   ` Christoph Hellwig
2016-07-11 16:12     ` J Freyensee
2016-07-11 20:29     ` Arnd Bergmann
2016-07-12 15:36       ` Jens Axboe [this message]
2016-07-12 15:38     ` Jens Axboe

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=57850E99.1080901@fb.com \
    --to=axboe@fb.com \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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).