From: teng sterling <sterlingteng@gmail.com>
To: yong w <yongw.pur@gmail.com>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <siyanteng@loongson.cn>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
wang.yong12@zte.com.cn, yang.yang29@zte.com.cn
Subject: Re: [PATCH] docs/zh_CN: Update zh_CN/accounting/delay-accounting.rst
Date: Wed, 19 Jan 2022 11:28:42 +0800 [thread overview]
Message-ID: <CAMU9jJr4A0jsZGAqdOUTc-gBeshCgPAS=2Vvubs_kmsJSegzkQ@mail.gmail.com> (raw)
In-Reply-To: <CAOH5QeAka4QsLCOHaNK8NBp1BUFsu3HqEqiOhWOewabA58fVqw@mail.gmail.com>
yong w <yongw.pur@gmail.com> 于2022年1月18日周二 20:38写道:
>
> Hello,
> Is this patch OK?
>
> yong w <yongw.pur@gmail.com> 于2022年1月13日周四 22:56写道:
> >
> > Hello,
> > teng sterling <sterlingteng@gmail.com> 于2022年1月13日周四 10:11写道:
> > >
> > > Hi Yong,
> > > <yongw.pur@gmail.com> 于2022年1月13日周四 07:27写道:
> > > >
> > > > From: wangyong <wang.yong12@zte.com.cn>
> > > >
> > > > Update zh_CN/accounting/delay-accounting.rst.
> > > > The document modification has been merged which refers to the following link:
> > > > https://lore.kernel.org/all/1639583021-92977-1-git-send-email-wang.yong12@zte.com.cn/
> > > The normal way to handle this is to add an appropriate Fixes tag.
Since 4d3959d65968(Documentation/accounting/delay-accounting.rst: add
thrashing page cache and direct compact) Modified the original
document,
It seems we forgot to update the Chinese documentation, let's update it now.
> > >
> > > By the way, this patch should be submitted together as part of that
> > > patch series where you modified the original documentation. Also check
> > > out the documentation for other languages and send it in the same way.
> > > If you get stuck, simply --CC the maintainer is an elegant way to
> > > handle it. >_<
> > The previous patch has been merged into linux-next. There was no
> > Chinese translation when I submitted it.
> > At present, this document is only translated into Chinese, which was
> > translated not long ago.
> > So I update it in this patch.
> > >
> > > >
> > > > Signed-off-by: wangyong <wang.yong12@zte.com.cn>
> > > > Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>
> > > This looks like the first version of the patch and doesn't seem to
> > > have been reviewed by anyone yet, so you can't sign it instead of
> > > someone else.
> > Yang Yang reviewed it offline.
I'm not sure if this is appropriate, but lore is missing the review
process and the mailing list developers don't know what's going on,
which in a way makes it more difficult for future developers to learn.
Apart from the above,LGTM.
Thanks,
Yanteng
> > >
> > > Thanks,
> > > Yanteng
> > Thanks for your reply.
next prev parent reply other threads:[~2022-01-19 3:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:04 yongw.pur
2022-01-13 2:11 ` teng sterling
2022-01-13 14:56 ` yong w
2022-01-18 12:38 ` yong w
2022-01-19 3:28 ` teng sterling [this message]
2022-01-19 3:41 ` Alex Shi
2022-01-27 18:38 ` Jonathan Corbet
2022-02-07 7:38 ` Alex Shi
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='CAMU9jJr4A0jsZGAqdOUTc-gBeshCgPAS=2Vvubs_kmsJSegzkQ@mail.gmail.com' \
--to=sterlingteng@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=siyanteng@loongson.cn \
--cc=wang.yong12@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=yongw.pur@gmail.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
all inboxes | Powered by JetHome®