From: Greg KH <gregkh@linuxfoundation.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: Daeho Jeong <daehojeong@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: add symbolic link to kobject in sysfs
Date: Fri, 3 Jul 2020 16:13:59 +0200 [thread overview]
Message-ID: <20200703141359.GA2953162@kroah.com> (raw)
In-Reply-To: <20200703065420.3544269-1-daeho43@gmail.com>
On Fri, Jul 03, 2020 at 03:54:20PM +0900, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Added a symbolic link to directory of sysfs. It will
> create a symbolic link such as "mount_0" and "mount_1" to
> each f2fs mount in the order of mounting filesystem. But
> once one mount point was umounted, that sequential number
> @x in "mount_@x" could be reused by later newly mounted
> point. It will provide easy access to sysfs node even if
> not knowing the specific device node name like sda19 and
> dm-3.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> Documentation/filesystems/f2fs.rst | 13 ++++++++++++-
No Documentation/ABI/ entry for your new sysfs file/link?
And what does this help with?
If it's really needed, why don't we do this for all filesystem types?
thanks,
greg k-h
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
Subject: Re: [PATCH v3] f2fs: add symbolic link to kobject in sysfs
Date: Fri, 3 Jul 2020 16:13:59 +0200 [thread overview]
Message-ID: <20200703141359.GA2953162@kroah.com> (raw)
In-Reply-To: <20200703065420.3544269-1-daeho43@gmail.com>
On Fri, Jul 03, 2020 at 03:54:20PM +0900, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Added a symbolic link to directory of sysfs. It will
> create a symbolic link such as "mount_0" and "mount_1" to
> each f2fs mount in the order of mounting filesystem. But
> once one mount point was umounted, that sequential number
> @x in "mount_@x" could be reused by later newly mounted
> point. It will provide easy access to sysfs node even if
> not knowing the specific device node name like sda19 and
> dm-3.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> Documentation/filesystems/f2fs.rst | 13 ++++++++++++-
No Documentation/ABI/ entry for your new sysfs file/link?
And what does this help with?
If it's really needed, why don't we do this for all filesystem types?
thanks,
greg k-h
next prev parent reply other threads:[~2020-07-03 14:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 6:54 [f2fs-dev] [PATCH v3] f2fs: add symbolic link to kobject in sysfs Daeho Jeong
2020-07-03 6:54 ` Daeho Jeong
2020-07-03 8:18 ` [f2fs-dev] " Chao Yu
2020-07-03 8:18 ` Chao Yu
2020-07-03 14:13 ` Greg KH [this message]
2020-07-03 14:13 ` Greg KH
2020-07-05 23:47 ` [f2fs-dev] " Daeho Jeong
2020-07-05 23:47 ` Daeho Jeong
2020-07-08 10:05 ` [f2fs-dev] " Greg KH
2020-07-08 10:05 ` Greg KH
2020-07-09 1:07 ` [f2fs-dev] " Daeho Jeong
2020-07-09 1:07 ` Daeho Jeong
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=20200703141359.GA2953162@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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.