From: Mike Christie <mchristi@redhat.com>
To: target-devel@vger.kernel.org
Subject: Re: [PATCH 11/15] target: export initiator port values for all sessions
Date: Thu, 19 Jul 2018 21:30:36 +0000 [thread overview]
Message-ID: <5B5102FC.8090204@redhat.com> (raw)
In-Reply-To: <1531696591-8558-12-git-send-email-mchristi@redhat.com>
On 07/19/2018 03:47 PM, Christoph Hellwig wrote:
> On Thu, Jul 19, 2018 at 05:07:59PM +0000, Bart Van Assche wrote:
>> Initially configfs did not support creation of a directory from the kernel
>> side. Last time I brought this up with Christoph he replied that this
>> functionality has been added to configfs (if I understood Christoph
>> correctly).
>
> I don't think the functionality was ever missing, but I might be
> mistaken. You can always call config_group_init_type_name() +
> configfs_add_default_group to add a directory. nvmet makes heavy
> use of that.
Just to clarify. We can create a dir from the kernel already. It is no
problem. I am doing that in this patchset with configfs_register_group.
What Bart was requesting originally and what is missing is being able to
add a symlink from the kernel.
I have not fully looked into it, but I think it would be something like
taking part of configfs_symlink and making it so we can call it with
config_items for the 2 items to be symlinked.
next prev parent reply other threads:[~2018-07-19 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 23:16 [PATCH 11/15] target: export initiator port values for all sessions Mike Christie
2018-07-18 22:41 ` Bart Van Assche
2018-07-18 23:04 ` Mike Christie
2018-07-19 2:15 ` Mike Christie
2018-07-19 15:37 ` Bart Van Assche
2018-07-19 15:38 ` Bart Van Assche
2018-07-19 16:38 ` Mike Christie
2018-07-19 17:07 ` Bart Van Assche
2018-07-19 20:47 ` Christoph Hellwig
2018-07-19 21:30 ` Mike Christie [this message]
2018-07-20 15:10 ` Christoph Hellwig
2018-08-01 16:44 ` Mike Christie
2018-08-01 17:11 ` Mike Christie
2018-08-01 17:38 ` 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=5B5102FC.8090204@redhat.com \
--to=mchristi@redhat.com \
--cc=target-devel@vger.kernel.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.