From: Chao Yu <yuchao0@huawei•com>
To: Jonathan Corbet <corbet@lwn•net>,
Stephen Rothwell <sfr@canb•auug.org.au>
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>
Subject: Re: linux-next: build warning after merge of the f2fs tree
Date: Mon, 11 Jan 2021 15:54:19 +0800 [thread overview]
Message-ID: <5918c348-666a-ee41-3891-ddcf500c464b@huawei.com> (raw)
In-Reply-To: <20210110163534.24481e1e@lwn.net>
Hi Jonathan,
On 2021/1/11 7:35, Jonathan Corbet wrote:
> On Mon, 11 Jan 2021 07:33:54 +1100
> Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
>> 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. >
> 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.
Copied, thanks for your reminder.
I've fixed it and resent the patch:
https://lore.kernel.org/linux-f2fs-devel/20210111075017.82370-1-yuchao0@huawei.com/T/#u
>
> Thanks,
>
> jon
> .
>
next prev parent reply other threads:[~2021-01-11 7:55 UTC|newest]
Thread overview: 18+ 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
2021-01-10 23:35 ` Jonathan Corbet
2021-01-11 7:54 ` Chao Yu [this message]
2021-01-12 5:09 ` Stephen Rothwell
2021-01-12 6:07 ` Chao Yu
-- strict thread matches above, loose matches on Subject: below --
2025-04-30 10:42 Stephen Rothwell
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=5918c348-666a-ee41-3891-ddcf500c464b@huawei.com \
--to=yuchao0@huawei$(echo .)com \
--cc=chao@kernel$(echo .)org \
--cc=corbet@lwn$(echo .)net \
--cc=jaegeuk@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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