mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dongliang Mu <dzm91@hust.edu.cn>
To: SeongJae Park <sj@kernel.org>, Doehyun Baek <doehyunbaek@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
	Hu Haowen <2023002089@link.tyut.edu.cn>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	damon@lists.linux.dev
Subject: Re: [PATCH v4 0/2] docs/mm/damon: fix docs and update zh_CN
Date: Wed, 10 Jun 2026 09:15:45 +0800	[thread overview]
Message-ID: <d2a6a7f1-96e1-4e6b-abfb-e9b13dff3561@hust.edu.cn> (raw)
In-Reply-To: <20260609235556.73472-1-sj@kernel.org>


On 6/10/26 7:55 AM, SeongJae Park wrote:
> Hello Doehyun,
>
> On Tue,  9 Jun 2026 14:34:24 +0000 Doehyun Baek <doehyunbaek@gmail.com> wrote:
>
>> First of all, thank you very much, Dongliang, for your time and
>> dedication in reviewing the previous versions.
>>
>> This v4 sends the original English DAMON documentation fixes as the
>> first patch, and the Simplified Chinese translation update as the
>> second patch.

Hi Doehyun,

I think my earlier message may have been unclear, so I’d like to clarify 
the points below.

First, as suggested by SeongJae Park, please submit a standalone patch 
to the |mm-new| or |linux-doc| tree to correct these typos.

Once this typo-fix patch is merged, you may proceed to submit the 
Chinese translation patches.

Additionally, please split patch 2/2 into two separate patches, with 
each patch covering changes to only one file.

Dongliang Mu

>>
>> For zh_CN, I translated the current DAMON usage.rst paragraph by
>> paragraph, and added missing pieces such as stat.rst and the related
>> index/design references.  The zh_TW changes from earlier versions are
>> dropped from this series.
> Thank you for sharing this patch series!  However, to my understanding, the
> path to the mainline for English documents and Chinese documents are different.
> Sending patches for English document and Chinese document as one series is
> therefore making it complicated, in my opinion.  Could you please rebase
> English document part to mm-new [1] and send as a separate patch?


Totally agree. Please follow this suggestion.


>
> [1] https://origin.kernel.org/doc/html/latest/mm/damon/maintainer-profile.html#scm-trees
>
>
> Thanks,
> SJ
>
> [...]


      reply	other threads:[~2026-06-10  1:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  9:44 [PATCH 0/2] docs/zh: update DAMON usage sysfs documentation Doehyun Baek
2026-05-23  9:44 ` [PATCH 1/2] docs/zh_CN: " Doehyun Baek
2026-05-23  9:44 ` [PATCH 2/2] docs/zh_TW: " Doehyun Baek
2026-06-08  2:12 ` [PATCH 0/2] docs/zh: " Dongliang Mu
2026-06-08  6:03 ` [PATCH v2 " Doehyun Baek
2026-06-08  6:03   ` [PATCH v2 1/2] docs/zh_CN: update DAMON usage Chinese translation Doehyun Baek
2026-06-08  6:03   ` [PATCH v2 2/2] docs/zh_TW: update DAMON usage Traditional " Doehyun Baek
     [not found]   ` <CAN-j9UrkjjrO-1fs9Q4_HQMTM5Gj1qjyNLF5F1JG+Wzimd5naw@mail.gmail.com>
2026-06-08  6:58     ` [PATCH v2 0/2] docs/zh: update DAMON usage sysfs documentation Dongliang Mu
2026-06-08  6:57 ` [PATCH v3 " Doehyun Baek
2026-06-08  6:57   ` [PATCH v3 1/2] docs/zh_CN: update DAMON usage Chinese translation Doehyun Baek
2026-06-08 12:29     ` Dongliang Mu
2026-06-08  6:57   ` [PATCH v3 2/2] docs/zh_TW: update DAMON usage Traditional " Doehyun Baek
2026-06-09 14:34 ` [PATCH v4 0/2] docs/mm/damon: fix docs and update zh_CN Doehyun Baek
2026-06-09 14:34   ` [PATCH v4 1/2] docs/mm/damon: fix DAMON documentation details Doehyun Baek
2026-06-09 14:34   ` [PATCH v4 2/2] docs/zh_CN: update DAMON documentation translation Doehyun Baek
2026-06-09 23:55   ` [PATCH v4 0/2] docs/mm/damon: fix docs and update zh_CN SeongJae Park
2026-06-10  1:15     ` Dongliang Mu [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=d2a6a7f1-96e1-4e6b-abfb-e9b13dff3561@hust.edu.cn \
    --to=dzm91@hust.edu.cn \
    --cc=2023002089@link.tyut.edu.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=doehyunbaek@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=sj@kernel.org \
    --cc=skhan@linuxfoundation.org \
    /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®