From: Jonathan Corbet <corbet@lwn.net>
To: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>, akpm@linux-foundation.org
Cc: akiyks@gmail.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rppt@kernel.org,
skhan@linuxfoundation.org, yejiajian2018@email.szu.edu.cn,
zhangyinan2019@email.szu.edu.cn,
Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
Subject: Re: [PATCH v4] Documentation/mm/page_owner.rst: delete frequently changing experimental data
Date: Mon, 10 Oct 2022 12:54:52 -0600 [thread overview]
Message-ID: <874jwbqzk3.fsf@meer.lwn.net> (raw)
In-Reply-To: <20221005145525.10359-1-caoyixuan2019@email.szu.edu.cn>
Yixuan Cao <caoyixuan2019@email.szu.edu.cn> writes:
> The kernel size changes due to many factors, such as compiler
> version, configuration, and the build environment. This makes
> size comparison figures irrelevant to reader's setup.
>
> Remove these figures and describe the effects of page owner
> to the kernel size in general instead.
>
> Thanks for Jonathan Corbet, Bagas Sanjaya and Mike Rapoport's
> constructive suggestions.
>
> Signed-off-by: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
> ---
> Documentation/mm/page_owner.rst | 20 ++++----------------
> 1 file changed, 4 insertions(+), 16 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2022-10-10 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 17:29 [PATCH] Documentation/mm/page_owner.rst: update " Yixuan Cao
2022-08-25 18:09 ` Jonathan Corbet
2022-08-26 2:30 ` Bagas Sanjaya
2022-08-26 4:16 ` Mike Rapoport
2022-10-05 9:10 ` [PATCH v2] Documentation/mm/page_owner.rst: delete frequently changing " Yixuan Cao
2022-10-05 9:32 ` Bagas Sanjaya
2022-10-05 11:38 ` [PATCH v3] " Yixuan Cao
2022-10-05 14:55 ` [PATCH v4] " Yixuan Cao
2022-10-06 1:46 ` Bagas Sanjaya
2022-10-06 4:05 ` [PATCH v5] " Yixuan Cao
2022-10-10 18:54 ` Jonathan Corbet [this message]
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=874jwbqzk3.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=akiyks@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=caoyixuan2019@email.szu.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rppt@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=yejiajian2018@email.szu.edu.cn \
--cc=zhangyinan2019@email.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
all inboxes | Powered by JetHome®