From: Dongliang Mu <mudongliangabcd@gmail.com>
To: Nick Huang <sef1548@gmail.com>
Cc: David Hildenbrand <david@redhat.com>,
alexs@kernel.org, si.yanteng@linux.dev, dzm91@hust.edu.cn,
corbet@lwn.net, akpm@linux-foundation.org,
wangkefeng.wang@huawei.com, vishal.moola@gmail.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/balloon_compaction: update Chinese docs for movable_ops
Date: Mon, 23 Jun 2025 17:12:24 +0800 [thread overview]
Message-ID: <CAD-N9QV5r4YyO6qbL477x0sJar2=WTdHH=x58P9Qatff_HC3Nw@mail.gmail.com> (raw)
In-Reply-To: <CABZAGRGvf9Ge5EvMgFP3FUHt2QOpq6xXe9nB4=it9zb+V1DNwg@mail.gmail.com>
On Mon, Jun 23, 2025 at 4:51 PM Nick Huang <sef1548@gmail.com> wrote:
>
> David Hildenbrand <david@redhat.com> 於 2025年6月23日 週一 下午4:08寫道：
> >
> > On 22.06.25 02:42, Nick Huang wrote:
> > > Remove Non-LRU Page Migration and Add Movable_ops Page Migration
> > >
> >
> > I'm afraid most people you CC on Chinese doc updates will not be able to
> > help in any reasonable way.
> >
> > --
> > Cheers,
> >
> > David / dhildenb
>
> How can I fix these things?
From my understanding, you can follow this how-to.rst[1] and submit
your patches.
This is more friendly for reviewers and maintainers.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/translations/zh_CN/how-to.rst
>
>
> --
> Regards,
> Nick Huang
>
next prev parent reply other threads:[~2025-06-23 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 0:42 Nick Huang
2025-06-22 13:33 ` [PATCH v2] " Nick Huang
2025-06-23 2:15 ` Dongliang Mu
2025-06-23 3:23 ` Nick Huang
2025-06-23 8:07 ` [PATCH] " David Hildenbrand
2025-06-23 8:50 ` Nick Huang
2025-06-23 9:12 ` Dongliang Mu [this message]
2025-06-23 9:23 ` David Hildenbrand
2025-06-23 9:35 ` Dongliang Mu
2025-06-23 9:38 ` David Hildenbrand
2025-06-23 9:14 ` Dongliang Mu
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='CAD-N9QV5r4YyO6qbL477x0sJar2=WTdHH=x58P9Qatff_HC3Nw@mail.gmail.com' \
--to=mudongliangabcd@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sef1548@gmail.com \
--cc=si.yanteng@linux.dev \
--cc=vishal.moola@gmail.com \
--cc=wangkefeng.wang@huawei.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