From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Christoph Hellwig <hch@lst.de>,
axboe@kernel.dk, keith.busch@intel.com,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: NVMe over Fabrics target implementation
Date: Tue, 7 Jun 2016 19:31:05 +0200 [thread overview]
Message-ID: <20160607173105.GA13935@lst.de> (raw)
In-Reply-To: <6abd6fd0-3a75-8569-95a4-174d856d0043@sandisk.com>
Hi Bart,
> As you know with configfs it is not allowed to create directories in the
> configfs hierarchy from inside the kernel.
Of course you can, and every user of configfs relies on being able
to create directories from the kernel using either the default_groups
list, or through the use of configfs_register_group().
WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: NVMe over Fabrics target implementation
Date: Tue, 7 Jun 2016 19:31:05 +0200 [thread overview]
Message-ID: <20160607173105.GA13935@lst.de> (raw)
In-Reply-To: <6abd6fd0-3a75-8569-95a4-174d856d0043@sandisk.com>
Hi Bart,
> As you know with configfs it is not allowed to create directories in the
> configfs hierarchy from inside the kernel.
Of course you can, and every user of configfs relies on being able
to create directories from the kernel using either the default_groups
list, or through the use of configfs_register_group().
next prev parent reply other threads:[~2016-06-07 17:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:22 NVMe over Fabrics target implementation Christoph Hellwig
2016-06-06 21:22 ` Christoph Hellwig
2016-06-06 21:22 ` [PATCH 1/3] block: Export blk_poll Christoph Hellwig
2016-06-06 21:22 ` Christoph Hellwig
2016-06-07 6:49 ` Nicholas A. Bellinger
2016-06-07 6:49 ` Nicholas A. Bellinger
2016-06-06 21:22 ` [PATCH 2/3] nvmet: add a generic NVMe target Christoph Hellwig
2016-06-06 21:22 ` Christoph Hellwig
2016-06-06 21:22 ` [PATCH 3/3] nvme-loop: add a NVMe loopback host driver Christoph Hellwig
2016-06-06 21:22 ` Christoph Hellwig
2016-06-06 22:00 ` kbuild test robot
2016-06-06 22:00 ` kbuild test robot
2016-06-07 6:23 ` NVMe over Fabrics target implementation Nicholas A. Bellinger
2016-06-07 6:23 ` Nicholas A. Bellinger
2016-06-07 6:23 ` Nicholas A. Bellinger
2016-06-07 10:55 ` Christoph Hellwig
2016-06-07 10:55 ` Christoph Hellwig
2016-06-08 5:21 ` Nicholas A. Bellinger
2016-06-08 5:21 ` Nicholas A. Bellinger
2016-06-08 12:19 ` Christoph Hellwig
2016-06-08 12:19 ` Christoph Hellwig
2016-06-08 13:12 ` Sagi Grimberg
2016-06-08 13:12 ` Sagi Grimberg
2016-06-08 13:46 ` Christoph Hellwig
2016-06-08 13:46 ` Christoph Hellwig
2016-06-09 4:36 ` Nicholas A. Bellinger
2016-06-09 4:36 ` Nicholas A. Bellinger
2016-06-09 13:46 ` Christoph Hellwig
2016-06-09 13:46 ` Christoph Hellwig
2016-06-09 13:46 ` Christoph Hellwig
2016-06-09 3:32 ` Nicholas A. Bellinger
2016-06-09 3:32 ` Nicholas A. Bellinger
2016-06-07 21:02 ` Andy Grover
2016-06-07 21:02 ` Andy Grover
2016-06-07 21:10 ` Ming Lin
2016-06-07 21:10 ` Ming Lin
2016-06-07 17:01 ` Bart Van Assche
2016-06-07 17:01 ` Bart Van Assche
2016-06-07 17:31 ` Christoph Hellwig [this message]
2016-06-07 17:31 ` Christoph Hellwig
2016-06-07 18:11 ` Bart Van Assche
2016-06-07 18:11 ` Bart Van Assche
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=20160607173105.GA13935@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@sandisk.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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.