Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: linux-next: build warning after merge of the f2fs tree
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        Jaegeuk Kim <jaegeuk@kernel.org>
CC:     Chao Yu <chao@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>
References: <20210107141158.312835d8@canb.auug.org.au>
From:   Chao Yu <yuchao0@huawei.com>
Message-ID: <3f921b3d-e8f2-e010-0f6b-76596e29e997@huawei.com>
Date:   Thu, 7 Jan 2021 19:28:19 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20210107141158.312835d8@canb.auug.org.au>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Stephen,

On 2021/1/7 11:11, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the f2fs tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> Documentation/ABI/testing/sysfs-fs-f2fs:382: WARNING: Inline emphasis start-string without end-string.

IIUC, should I remove "/*" and "*/" for newly added entry in sysfs-fs-f2fs?

+What:		/sys/fs/f2fs/<disk>/stat/sb_status
+Date:		December 2020
+Contact:	"Chao Yu" <yuchao0@huawei.com>
+Description:	Show status of f2fs superblock in real time.
+
+		value           sb status macro                 description
+		0x1             SBI_IS_DIRTY,                   /* dirty flag for checkpoint */
+		0x2             SBI_IS_CLOSE,                   /* specify unmounting */
+		0x4             SBI_NEED_FSCK,                  /* need fsck.f2fs to fix */
...

Thanks,

> 
> Introduced by commit
> 
>    f23307575903 ("f2fs: introduce sb_status sysfs node")
>