[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200703141359.GA2953162@kroah.com>
Date: Fri, 3 Jul 2020 16:13:59 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Daeho Jeong <daeho43@...il.com>
Cc: linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, kernel-team@...roid.com,
Daeho Jeong <daehojeong@...gle.com>
Subject: Re: [PATCH v3] f2fs: add symbolic link to kobject in sysfs
On Fri, Jul 03, 2020 at 03:54:20PM +0900, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@...gle.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@...gle.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
Powered by blists - more mailing lists