From: Akira Yokosawa <akiyks@gmail.com>
To: Shenghong Han <hanshenghong2019@email.szu.edu.cn>, corbet@lwn.net
Cc: akpm@linux-foundation.org, baihaowen@meizu.com,
seakeel@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, caoyixuan2019@email.szu.edu.cn,
yejiajian2018@email.szu.edu.cn, yuhongf@szu.edu.cn
Subject: Re: [PATCH] Documentation/vm/page_owner.rst: Fix syntax error and Describe details using table
Date: Sat, 30 Apr 2022 09:57:19 +0900 [thread overview]
Message-ID: <83176583-f392-ed9c-a4a2-9d8f67c0fd19@gmail.com> (raw)
In-Reply-To: <20220429181926.10658-1-hanshenghong2019@email.szu.edu.cn>
Hi,
On Sat, 30 Apr 2022 02:19:26 +0800,
Shenghong Han wrote:
> Subject: [PATCH] Documentation/vm/page_owner.rst: ...
This is v2 of the patch, isn't it? If so, it should be indicated
in the prefix as "[PATCH v2]".
> Some syntax errors exist in "page_owner.rst". Thanks to Akira Yokosawa and
> Haowen Bai for tips to help improve the documentation.>
> We try to fix them. Hope that the Documentation is showed as we expect.
In changelog, describe technical facts. Not what you think or hope.
You need to do a respin with a better explanation at least.
Hint: A fix without using tables would be the simplest. Please look
at the changes in the preceding section I made in commit 5603f9bdea68
("docs: vm/page_owner: use literal blocks for param description").
You are seeing the build error because a literal block ends at a next
line which starts from column 1.
I don't think Jon would dislike the simplest approach. :-)
Of course, if you guys love tables so much, I don't mind.
>
> Signed-off-by: Shenghong Han <hanshenghong2019@email.szu.edu.cn>
> Fixes: edc93abbcc6d ("tools/vm/page_owner_sort.c: support sorting blocks by multiple keys")
SHA-1 ID of a not-yet-merged commit will likely break later in
the merge window.
Good luck!
Thanks, Akira
>
> ---
> Thanks Jonathan's suggestion.
>
> This fix is a simpler than before.
> And yes, It has built in my machine.
>
> Best,
>
> Shenghong Han
> ---
> ---
> Documentation/vm/page_owner.rst | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/vm/page_owner.rst b/Documentation/vm/page_owner.rst
> index 25622c715..0ecb4a739 100644
> --- a/Documentation/vm/page_owner.rst
> +++ b/Documentation/vm/page_owner.rst
[...]
next prev parent reply other threads:[~2022-04-30 0:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 18:19 [PATCH] Documentation/vm/page_owner.rst: Fix syntax error and Describe details using table Shenghong Han
2022-04-30 0:57 ` Akira Yokosawa [this message]
2022-04-30 6:40 ` Akira Yokosawa
2022-04-30 8:13 ` Shenghong Han
2022-04-30 8:29 ` Akira Yokosawa
2022-04-30 10:25 ` Resend: " Shenghong Han
2022-05-02 1:44 ` Akira Yokosawa
-- strict thread matches above, loose matches on Subject: below --
2022-04-29 17:18 Shenghong Han
2022-04-29 17:29 ` Jonathan Corbet
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=83176583-f392-ed9c-a4a2-9d8f67c0fd19@gmail.com \
--to=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baihaowen@meizu.com \
--cc=caoyixuan2019@email.szu.edu.cn \
--cc=corbet@lwn.net \
--cc=hanshenghong2019@email.szu.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seakeel@gmail.com \
--cc=yejiajian2018@email.szu.edu.cn \
--cc=yuhongf@szu.edu.cn \
/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).