From: Akira Yokosawa <akiyks@gmail.com>
To: Shenghong Han <hanshenghong2019@email.szu.edu.cn>,
Jonathan Corbet <corbet@lwn.net>
Cc: akpm <akpm@linux-foundation.org>, baihaowen <baihaowen@meizu.com>,
seakeel <seakeel@gmail.com>,
linux-doc <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
caoyixuan2019 <caoyixuan2019@email.szu.edu.cn>,
yejiajian2018 <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 17:29:02 +0900 [thread overview]
Message-ID: <4a68c764-1467-d384-0b92-8dea03f914d2@gmail.com> (raw)
In-Reply-To: <tencent_088763F35CE233FB6C9CEB80@qq.com>
Hi,
Sorry, I don't read such a broken (no line breaks at all) message.
Please check your e-mail client settings so that it can send proper
plain-text messages.
I can test the receiving side privately.
--
Akira
On 2022/04/30 17:13, Shenghong Han wrote:
> 0) If you have received a similar reply, please refer to the latest reply.1) Accidentally used Chinese Input Method Editor, leaving full-width symbols during the test, causing the double dashes of "--" changed
[snip]
next prev parent reply other threads:[~2022-04-30 8:29 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
2022-04-30 6:40 ` Akira Yokosawa
2022-04-30 8:13 ` Shenghong Han
2022-04-30 8:29 ` Akira Yokosawa [this message]
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=4a68c764-1467-d384-0b92-8dea03f914d2@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).