linux-kernel - Re: linux-next: build warning after merge of the f2fs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 10 Jan 2021 16:35:34 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Chao Yu <yuchao0@...wei.com>, Jaegeuk Kim <jaegeuk@...nel.org>,
        Chao Yu <chao@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the f2fs tree

On Mon, 11 Jan 2021 07:33:54 +1100
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> On Thu, 7 Jan 2021 19:28:19 +0800 Chao Yu <yuchao0@...wei.com> wrote:
> >
> > On 2021/1/7 11:11, Stephen Rothwell wrote:  
> > > 
> > > 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?  
> 
> Sorry, I don't know.  Cc'ing Jon.

Removing the comment markers would make the warning go away, but won't
lead to a satisfactory rendering in HTML.  If you want that too, make the
table look like the others immediately above it in the same file.

Thanks,

jon