From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: Hridya Valsaraju <hridya@google.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH 1/2] f2fs: delete duplicate information on sysfs nodes
Date: Fri, 25 Oct 2019 11:23:25 -0700 [thread overview]
Message-ID: <20191025182325.GC24183@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <edc52873-b40d-5047-dba0-d693548eb16d@huawei.com>
On 10/24, Chao Yu wrote:
> On 2019/10/24 5:48, Hridya Valsaraju wrote:
> > This patch merges the sysfs node documentation present in
> > Documentation/filesystems/f2fs.txt and
> > Documentation/ABI/testing/sysfs-fs-f2fs
> > and deletes the duplicate information from
> > Documentation/filesystems/f2fs.txt. This is to prevent having to update
> > both files when a new sysfs node is added for f2fs.
> > The patch also makes minor formatting changes to
> > Documentation/ABI/testing/sysfs-fs-f2fs.
>
> Jaegeuk, any particular reason to add duplicated description on f2fs.txt previously?
Not at all, thus, I asked Hridya to consolidate them. :P
>
> Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Hridya Valsaraju <hridya@google.com>,
kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: delete duplicate information on sysfs nodes
Date: Fri, 25 Oct 2019 11:23:25 -0700 [thread overview]
Message-ID: <20191025182325.GC24183@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <edc52873-b40d-5047-dba0-d693548eb16d@huawei.com>
On 10/24, Chao Yu wrote:
> On 2019/10/24 5:48, Hridya Valsaraju wrote:
> > This patch merges the sysfs node documentation present in
> > Documentation/filesystems/f2fs.txt and
> > Documentation/ABI/testing/sysfs-fs-f2fs
> > and deletes the duplicate information from
> > Documentation/filesystems/f2fs.txt. This is to prevent having to update
> > both files when a new sysfs node is added for f2fs.
> > The patch also makes minor formatting changes to
> > Documentation/ABI/testing/sysfs-fs-f2fs.
>
> Jaegeuk, any particular reason to add duplicated description on f2fs.txt previously?
Not at all, thus, I asked Hridya to consolidate them. :P
>
> Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-10-25 18:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 21:48 [PATCH 1/2] f2fs: delete duplicate information on sysfs nodes Hridya Valsaraju
2019-10-23 21:48 ` [f2fs-dev] " Hridya Valsaraju via Linux-f2fs-devel
2019-10-23 21:48 ` [PATCH 2/2] f2fs: Add f2fs stats to sysfs Hridya Valsaraju
2019-10-23 21:48 ` [f2fs-dev] " Hridya Valsaraju via Linux-f2fs-devel
2019-10-24 9:26 ` Chao Yu
2019-10-24 9:26 ` [f2fs-dev] " Chao Yu
2019-10-25 3:51 ` Hridya Valsaraju
2019-10-25 3:51 ` [f2fs-dev] " Hridya Valsaraju via Linux-f2fs-devel
2019-10-25 8:30 ` Chao Yu
2019-10-25 8:30 ` [f2fs-dev] " Chao Yu
2019-10-25 18:22 ` Jaegeuk Kim
2019-10-25 18:22 ` [f2fs-dev] " Jaegeuk Kim
2019-10-26 1:37 ` Chao Yu
2019-10-26 1:37 ` [f2fs-dev] " Chao Yu
2019-10-29 0:26 ` Hridya Valsaraju
2019-10-29 0:26 ` [f2fs-dev] " Hridya Valsaraju via Linux-f2fs-devel
2019-10-24 9:15 ` [PATCH 1/2] f2fs: delete duplicate information on sysfs nodes Chao Yu
2019-10-24 9:15 ` [f2fs-dev] " Chao Yu
2019-10-25 18:23 ` Jaegeuk Kim [this message]
2019-10-25 18:23 ` Jaegeuk Kim
2019-10-26 1:40 ` Chao Yu
2019-10-26 1:40 ` [f2fs-dev] " Chao Yu
2020-01-23 1:13 Jaegeuk Kim
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=20191025182325.GC24183@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=corbet@lwn.net \
--cc=hridya@google.com \
--cc=kernel-team@android.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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.