From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chao Yu <yuchao0@huawei.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: linux-next: build warning after merge of the f2fs tree
Date: Mon, 11 Jan 2021 07:33:54 +1100 [thread overview]
Message-ID: <20210111073354.6ec0bbb5@canb.auug.org.au> (raw)
In-Reply-To: <3f921b3d-e8f2-e010-0f6b-76596e29e997@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
Hi Chao,
On Thu, 7 Jan 2021 19:28:19 +0800 Chao Yu <yuchao0@huawei.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.
>
> +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")
> >
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-10 20:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 3:11 linux-next: build warning after merge of the f2fs tree Stephen Rothwell
2021-01-07 11:28 ` Chao Yu
2021-01-10 20:33 ` Stephen Rothwell [this message]
2021-01-10 23:35 ` Jonathan Corbet
2021-01-11 7:54 ` Chao Yu
2021-01-12 5:09 ` Stephen Rothwell
2021-01-12 6:07 ` Chao Yu
-- strict thread matches above, loose matches on Subject: below --
2021-03-02 22:23 Stephen Rothwell
2021-03-03 19:27 ` Jaegeuk Kim
2018-11-26 0:19 Stephen Rothwell
2018-11-26 21:59 ` Jaegeuk Kim
2018-11-26 22:17 ` Stephen Rothwell
2018-11-26 22:22 ` Jaegeuk Kim
2018-11-26 22:36 ` Gustavo A. R. Silva
2018-11-26 22:40 ` Stephen Rothwell
2017-02-09 23:51 Stephen Rothwell
2017-02-10 0:01 ` 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=20210111073354.6ec0bbb5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chao@kernel.org \
--cc=corbet@lwn.net \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).