From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 850F2CA9EA0 for ; Sat, 26 Oct 2019 01:40:19 +0000 (UTC) Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 56C3521D7F; Sat, 26 Oct 2019 01:40:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sourceforge.net header.i=@sourceforge.net header.b="F36mIUht"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=sf.net header.i=@sf.net header.b="XB39g4P1" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 56C3521D7F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linux-f2fs-devel-bounces@lists.sourceforge.net Received: from [127.0.0.1] (helo=sfs-ml-4.v29.lw.sourceforge.com) by sfs-ml-4.v29.lw.sourceforge.com with esmtp (Exim 4.90_1) (envelope-from ) id 1iOB3y-0006wA-Uf; Sat, 26 Oct 2019 01:40:18 +0000 Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-4.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1iOB3x-0006vu-AW for linux-f2fs-devel@lists.sourceforge.net; Sat, 26 Oct 2019 01:40:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:CC:To:Subject:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=3v2ztA4o/sNwsRSW6c1lbqYpSCPTCS/itgoGRoKDk+M=; b=F36mIUhtjsDHb5Z7CR2EEB5OkL HmLQk8Wm6cwMzRMjhL2UIVhvdPh4aEhbFWodGbZa/Rvidi40+WO0Vi99qAEsw2P8YKgzVNEXb6Mh5 IVFxIJN9q9nGN/As/HfvYskiMUB/adb6Xz86aAiu26JQTryd3fVSvmXbK1vabsMSnk6Y=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:CC:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=3v2ztA4o/sNwsRSW6c1lbqYpSCPTCS/itgoGRoKDk+M=; b=XB39g4P1KKi/iGSf8it151KgjU nEpoVa1Goj9TlowkhMPA3FvEsAHZdScbFbohvG0N/Oiwcmgg2fe9BIKUYabi9L5qfQLp7kYlanMTX Q4MU/gTeL6q+lIEeoZ32phkveHD7bpS+TumyO3UiI9BFlu8TLxV1liCBA5tcDhWy1sok=; Received: from szxga07-in.huawei.com ([45.249.212.35] helo=huawei.com) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.2) id 1iOB3v-00HOwg-1T for linux-f2fs-devel@lists.sourceforge.net; Sat, 26 Oct 2019 01:40:17 +0000 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id C28C73ADE1FA7A9539E2; Sat, 26 Oct 2019 09:40:07 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.208) with Microsoft SMTP Server (TLS) id 14.3.439.0; Sat, 26 Oct 2019 09:40:03 +0800 To: Jaegeuk Kim References: <20191023214821.107615-1-hridya@google.com> <20191025182325.GC24183@jaegeuk-macbookpro.roam.corp.google.com> From: Chao Yu Message-ID: <6d09b590-053f-98ad-e628-2c352d989f01@huawei.com> Date: Sat, 26 Oct 2019 09:40:02 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20191025182325.GC24183@jaegeuk-macbookpro.roam.corp.google.com> Content-Language: en-US X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected X-Headers-End: 1iOB3v-00HOwg-1T Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: delete duplicate information on sysfs nodes X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-doc@vger.kernel.org, Jonathan Corbet , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, Hridya Valsaraju , kernel-team@android.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net 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 Thanks, > >> >> Thanks, > . > _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel