mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
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: Sat, 26 Oct 2019 09:40:02 +0800	[thread overview]
Message-ID: <6d09b590-053f-98ad-e628-2c352d989f01@huawei.com> (raw)
In-Reply-To: <20191025182325.GC24183@jaegeuk-macbookpro.roam.corp.google.com>

On 2019/10/26 2:23, Jaegeuk Kim wrote:
> 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

Alright...

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

> 
>>
>> Thanks,
> .
> 

  reply	other threads:[~2019-10-26  1:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 21:48 Hridya Valsaraju
2019-10-23 21:48 ` [PATCH 2/2] f2fs: Add f2fs stats to sysfs Hridya Valsaraju
2019-10-24  9:26   ` Chao Yu
2019-10-25  3:51     ` Hridya Valsaraju
2019-10-25  8:30       ` Chao Yu
2019-10-25 18:22         ` Jaegeuk Kim
2019-10-26  1:37           ` Chao Yu
2019-10-29  0:26             ` Hridya Valsaraju
2019-10-24  9:15 ` [PATCH 1/2] f2fs: delete duplicate information on sysfs nodes Chao Yu
2019-10-25 18:23   ` Jaegeuk Kim
2019-10-26  1:40     ` Chao Yu [this message]
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=6d09b590-053f-98ad-e628-2c352d989f01@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=corbet@lwn.net \
    --cc=hridya@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=kernel-team@android.com \
    --cc=linux-doc@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®