What's cooking in zh_CN (Jul 2026)

What's cooking in zh_CN (Jul 2026)

[Weijie Yuan]

Hi all,

Since I made many noise these days on the list, which took up a lot of
maintainers' time. This email summarizes the patches for zh_CN that are
currently pending on the mailing list.

-----------------------------------------------------------------------

* Ben Guo (2026-07-13) 4 commits
  [PATCH v2 0/4] docs/zh_CN: update rust documentation translations
  [PATCH v2 1/4] docs/zh_CN: Update rust/quick-start.rst translation
  [PATCH v2 2/4] docs/zh_CN: Update rust/general-information.rst translation
  [PATCH v2 3/4] docs/zh_CN: Update rust/arch-support.rst translation
  [PATCH v2 4/4] docs/zh_CN: Update rust/testing.rst translation

  Reviewed by Dongliang, a part needs to be revised. Expecting a reroll.

  cf. https://lore.kernel.org/linux-doc/17094968-1385-4dba-aae8-5d93a2aaf59e@hust.edu.cn/
  source: https://lore.kernel.org/linux-doc/cover.1783905132.git.ben.guo@openatom.club/

* Doehyun Baek (2026-07-08) 7 commits
  [PATCH v6 0/7] docs/zh_CN: update DAMON translations
  [PATCH v6 1/7] docs/zh_CN: update DAMON design translation
  [PATCH v6 2/7] docs/zh_CN: add DAMON_STAT usage translation
  [PATCH v6 3/7] docs/zh_CN: update DAMON index translation
  [PATCH v6 4/7] docs/zh_CN: update DAMON start translation
  [PATCH v6 5/7] docs/zh_CN: update DAMON usage translation
  [PATCH v6 6/7] docs/zh_CN: update DAMON reclaim translation
  [PATCH v6 7/7] docs/zh_CN: update DAMON LRU sort translation

  Needs review.

  source: https://lore.kernel.org/linux-doc/20260708073246.1652828-1-doehyunbaek@gmail.com/

* Jiandong Qiu 2026-07-06 2 commits
  [PATCH v3 0/2] docs/zh_CN: update translation of doc-guide/sphinx.rst
  [PATCH v3 1/2] docs/zh_CN: add process/changes.rst translation
  [PATCH v3 2/2] docs/zh_CN: update sphinx.rst translation

  Waiting for response(s) to review comment(s). & Needs review.

  cf. https://lore.kernel.org/linux-doc/ak1SG5mw7y2UZrvR@wyuan.org/
  source: https://lore.kernel.org/linux-doc/20260706151358.2103703-1-qiujiandong1998@gmail.com/

* Yan Zhu (2026-06-12) 10 commits
  [not found] <cover.1781105672.git.zhuyan2015@qq.com>
  [PATCH 01/10] docs/zh_CN: add LSM/index Chinese translation
  [PATCH 02/10] docs/zh_CN: add LSM/apparmor Chinese translation
  [PATCH 03/10] docs/zh_CN: add LSM/LoadPin Chinese translation
  [PATCH 04/10] docs/zh_CN: add LSM/SELinux Chinese translation
  [PATCH 05/10] docs/zh_CN: add LSM/Smack Chinese translation
  [PATCH 06/10] docs/zh_CN: add LSM/tomoyo Chinese translation
  [PATCH 07/10] docs/zh_CN: add LSM/Yama Chinese translation
  [PATCH 08/10] docs/zh_CN: add LSM/SafeSetID Chinese translation
  [PATCH 09/10] docs/zh_CN: add LSM/ipe Chinese translation
  [PATCH 10/10] docs/zh_CN: add LSM/landlock Chinese translation

  Needs review.

  source: https://lore.kernel.org/linux-doc/tencent_7080BF6BB8F05936649DDC091FFD8C45210A@qq.com/
  Note: cover letter missing on lore archive.

* chengyaqiang (2026-05-22) 1 commit
  [PATCH] docs/zh_CN: fix KASAN SW_TAGS mode description

  Reviewed by Dongliang and Zenghui, will merge to docs-next @alex ?

  source: https://lore.kernel.org/linux-doc/20260522075735.2022734-1-chengyaqiang@chengyaqiang.com/

* Haoyang Liu (2026-03-05) 1 commit
  [PATCH] docs/zh_CN: fix an inconsistent statement in dev-tools/testing-overview

  Expecting a reroll.

  cf. https://lore.kernel.org/linux-doc/29bd0dbc-c6f9-43ce-b95f-4e787e3fe9c3@gmail.com/
  source: https://lore.kernel.org/linux-doc/20260305192048.16405-1-tttturtleruss@gmail.com/

-----------------------------------------------------------------------

Okay, I have checked the 200 most recent messages on the mailing list,
going back to 15:09 UTC on February 25, 2026. If I have missed anything,
or I made a mistake somewhere, please let me know.

As you may have noticed, I borrowed (stole) this idea from Junio C
Hamano. Sending this kind of message, somewhat like a weekly status
report, not only helps maintainers keep track of outstanding work, but
also lets contributors know the current status of their patches.

More importantly, it gives newcomers an overview of the current state of
the project. New contributors can begin not only by submitting patches,
but also by reviewing patches already posted to the mailing list,
thereby learning how our workflow operates. This may also help reduce
the review burden on our friendly maintainers.

I would like to try this kind of periodic report as an experimental
effort, with its frequency adjusted according to the size of the patch
backlog and the level of activity on the mailing list. What do you
think? Please feel free to make comments.

By the way, I borrowed the subject line directly from Git's "What's
cooking in git.git". Does anyone have a better suggestion for the name? ;-)

Thanks,
Weijie

Re: What's cooking in zh_CN (Jul 2026)

[Alex Shi]

On 2026/7/14 00:49, Weijie Yuan wrote:
> Hi all,
> 
> Since I made many noise these days on the list, which took up a lot of
> maintainers' time. This email summarizes the patches for zh_CN that are
> currently pending on the mailing list.
> 
It's a great summary.

Contribution isn't only from submit patches, but also from actively 
document build, review, status update!

Thanks for you all!

Re: What's cooking in zh_CN (Jul 2026)

[Jiandong Qiu]

Hi,

This is great! As a newcomer, I often wondered what was going on, and
worried about duplicating others' work.

This kind of summary would really help newcomers get up to speed.

> More importantly, it gives newcomers an overview of the current state of
> the project. New contributors can begin not only by submitting patches,
> but also by reviewing patches already posted to the mailing list,
> thereby learning how our workflow operates. This may also help reduce
> the review burden on our friendly maintainers.

Just a thought: zh_CN/how-to.rst currently focuses mainly on submitting
patches. If we want to encourage newcomers to review too, maybe we could
add some guidance there on how to review, what to check and how to give
feedback? Curious what others think.

Thanks for starting this!

Best,

Jiandong

Re: What's cooking in zh_CN (Jul 2026)

[Weijie Yuan]

On Tue, Jul 14, 2026 at 10:30:24AM +0800, Jiandong Qiu wrote:
> Just a thought: zh_CN/how-to.rst currently focuses mainly on submitting
> patches. If we want to encourage newcomers to review too, maybe we could
> add some guidance there on how to review, what to check and how to give
> feedback? Curious what others think.

Yeah, Although the current situation indicates that the pressure of
review is not very high at present, gradually distributing the review
work to the community would definitely not be a bad thing. Finally, it
would be best to have Alex, Dongliang and Yanteng handle the last pass.

I see that most of the patches are currently reviewed by Dongliang. This
is definitely fine, but having more pairs of eyes would be even better,
just as Linus Torvalds said.

For how-to.rst, maybe we can add a section?

btw, Git has a doc especially for review:

  https://git-scm.com/docs/ReviewingGuidelines

we can have a look, then let's see what we can do.

Re: What's cooking in zh_CN (Jul 2026)

[Dongliang Mu]

On Tue, Jul 14, 2026 at 12:51 AM Weijie Yuan <wy@wyuan.org> wrote:
>
> Hi all,
>
> Since I made many noise these days on the list, which took up a lot of
> maintainers' time. This email summarizes the patches for zh_CN that are
> currently pending on the mailing list.

This is awesome. Maybe we can establish a dashboard for the activities
in zh_CN/TW related patches of linux-doc.

I personally kept a knowledge base in the IMA (an app for storing
knowledge base in the cloud) in our club to monitor these activities.

Dongliang Mu

>
> -----------------------------------------------------------------------
>
> * Ben Guo (2026-07-13) 4 commits
>   [PATCH v2 0/4] docs/zh_CN: update rust documentation translations
>   [PATCH v2 1/4] docs/zh_CN: Update rust/quick-start.rst translation
>   [PATCH v2 2/4] docs/zh_CN: Update rust/general-information.rst translation
>   [PATCH v2 3/4] docs/zh_CN: Update rust/arch-support.rst translation
>   [PATCH v2 4/4] docs/zh_CN: Update rust/testing.rst translation
>
>   Reviewed by Dongliang, a part needs to be revised. Expecting a reroll.
>
>   cf. https://lore.kernel.org/linux-doc/17094968-1385-4dba-aae8-5d93a2aaf59e@hust.edu.cn/
>   source: https://lore.kernel.org/linux-doc/cover.1783905132.git.ben.guo@openatom.club/
>
> * Doehyun Baek (2026-07-08) 7 commits
>   [PATCH v6 0/7] docs/zh_CN: update DAMON translations
>   [PATCH v6 1/7] docs/zh_CN: update DAMON design translation
>   [PATCH v6 2/7] docs/zh_CN: add DAMON_STAT usage translation
>   [PATCH v6 3/7] docs/zh_CN: update DAMON index translation
>   [PATCH v6 4/7] docs/zh_CN: update DAMON start translation
>   [PATCH v6 5/7] docs/zh_CN: update DAMON usage translation
>   [PATCH v6 6/7] docs/zh_CN: update DAMON reclaim translation
>   [PATCH v6 7/7] docs/zh_CN: update DAMON LRU sort translation

Maybe I can take a review tomorrow.

>
>   Needs review.
>
>   source: https://lore.kernel.org/linux-doc/20260708073246.1652828-1-doehyunbaek@gmail.com/
>
> * Jiandong Qiu 2026-07-06 2 commits
>   [PATCH v3 0/2] docs/zh_CN: update translation of doc-guide/sphinx.rst
>   [PATCH v3 1/2] docs/zh_CN: add process/changes.rst translation
>   [PATCH v3 2/2] docs/zh_CN: update sphinx.rst translation
>
>   Waiting for response(s) to review comment(s). & Needs review.
>
>   cf. https://lore.kernel.org/linux-doc/ak1SG5mw7y2UZrvR@wyuan.org/
>   source: https://lore.kernel.org/linux-doc/20260706151358.2103703-1-qiujiandong1998@gmail.com/
>
> * Yan Zhu (2026-06-12) 10 commits
>   [not found] <cover.1781105672.git.zhuyan2015@qq.com>
>   [PATCH 01/10] docs/zh_CN: add LSM/index Chinese translation
>   [PATCH 02/10] docs/zh_CN: add LSM/apparmor Chinese translation
>   [PATCH 03/10] docs/zh_CN: add LSM/LoadPin Chinese translation
>   [PATCH 04/10] docs/zh_CN: add LSM/SELinux Chinese translation
>   [PATCH 05/10] docs/zh_CN: add LSM/Smack Chinese translation
>   [PATCH 06/10] docs/zh_CN: add LSM/tomoyo Chinese translation
>   [PATCH 07/10] docs/zh_CN: add LSM/Yama Chinese translation
>   [PATCH 08/10] docs/zh_CN: add LSM/SafeSetID Chinese translation
>   [PATCH 09/10] docs/zh_CN: add LSM/ipe Chinese translation
>   [PATCH 10/10] docs/zh_CN: add LSM/landlock Chinese translation
>
>   Needs review.
>
>   source: https://lore.kernel.org/linux-doc/tencent_7080BF6BB8F05936649DDC091FFD8C45210A@qq.com/
>   Note: cover letter missing on lore archive.
>
> * chengyaqiang (2026-05-22) 1 commit
>   [PATCH] docs/zh_CN: fix KASAN SW_TAGS mode description
>
>   Reviewed by Dongliang and Zenghui, will merge to docs-next @alex ?
>
>   source: https://lore.kernel.org/linux-doc/20260522075735.2022734-1-chengyaqiang@chengyaqiang.com/
>
> * Haoyang Liu (2026-03-05) 1 commit
>   [PATCH] docs/zh_CN: fix an inconsistent statement in dev-tools/testing-overview
>
>   Expecting a reroll.
>
>   cf. https://lore.kernel.org/linux-doc/29bd0dbc-c6f9-43ce-b95f-4e787e3fe9c3@gmail.com/
>   source: https://lore.kernel.org/linux-doc/20260305192048.16405-1-tttturtleruss@gmail.com/
>
> -----------------------------------------------------------------------
>
> Okay, I have checked the 200 most recent messages on the mailing list,
> going back to 15:09 UTC on February 25, 2026. If I have missed anything,
> or I made a mistake somewhere, please let me know.
>
> As you may have noticed, I borrowed (stole) this idea from Junio C
> Hamano. Sending this kind of message, somewhat like a weekly status
> report, not only helps maintainers keep track of outstanding work, but
> also lets contributors know the current status of their patches.

As mentioned before, can we have a dashboard to see the status of
patches in zh_CN/TW? This is more useful in my mind.

>
> More importantly, it gives newcomers an overview of the current state of
> the project. New contributors can begin not only by submitting patches,
> but also by reviewing patches already posted to the mailing list,
> thereby learning how our workflow operates. This may also help reduce
> the review burden on our friendly maintainers.
>
> I would like to try this kind of periodic report as an experimental
> effort, with its frequency adjusted according to the size of the patch
> backlog and the level of activity on the mailing list. What do you
> think? Please feel free to make comments.

I think this is fine since linux-doc or narrowly zh_CN/TW do not have
many volumes of patches per day.

>
> By the way, I borrowed the subject line directly from Git's "What's
> cooking in git.git". Does anyone have a better suggestion for the name? ;-)

fine with this title

>
> Thanks,
> Weijie
>

Re: What's cooking in zh_CN (Jul 2026)

[Weijie Yuan]

On Tue, Jul 14, 2026 at 05:32:12PM +0800, Dongliang Mu wrote:
> On Tue, Jul 14, 2026 at 12:51 AM Weijie Yuan <wy@wyuan.org> wrote:
> >
> > Hi all,
> >
> > Since I made many noise these days on the list, which took up a lot of
> > maintainers' time. This email summarizes the patches for zh_CN that are
> > currently pending on the mailing list.
> 
> This is awesome. Maybe we can establish a dashboard for the activities
> in zh_CN/TW related patches of linux-doc.
> 
> I personally kept a knowledge base in the IMA (an app for storing
> knowledge base in the cloud) in our club to monitor these activities.

I remember kernel.org itself already provides this:

  https://patchwork.kernel.org/

Is this similar to your idea? But I haven't look deep into patchwork
before.

Of source, having our own thing is definitely okay.

> > * Doehyun Baek (2026-07-08) 7 commits
> >   [PATCH v6 0/7] docs/zh_CN: update DAMON translations
> >   [PATCH v6 1/7] docs/zh_CN: update DAMON design translation
> >   [PATCH v6 2/7] docs/zh_CN: add DAMON_STAT usage translation
> >   [PATCH v6 3/7] docs/zh_CN: update DAMON index translation
> >   [PATCH v6 4/7] docs/zh_CN: update DAMON start translation
> >   [PATCH v6 5/7] docs/zh_CN: update DAMON usage translation
> >   [PATCH v6 6/7] docs/zh_CN: update DAMON reclaim translation
> >   [PATCH v6 7/7] docs/zh_CN: update DAMON LRU sort translation
> 
> Maybe I can take a review tomorrow.

No rush of course ;-)

> > Okay, I have checked the 200 most recent messages on the mailing list,
> > going back to 15:09 UTC on February 25, 2026. If I have missed anything,
> > or I made a mistake somewhere, please let me know.
> >
> > As you may have noticed, I borrowed (stole) this idea from Junio C
> > Hamano. Sending this kind of message, somewhat like a weekly status
> > report, not only helps maintainers keep track of outstanding work, but
> > also lets contributors know the current status of their patches.
> 
> As mentioned before, can we have a dashboard to see the status of
> patches in zh_CN/TW? This is more useful in my mind.
> 
> >
> > More importantly, it gives newcomers an overview of the current state of
> > the project. New contributors can begin not only by submitting patches,
> > but also by reviewing patches already posted to the mailing list,
> > thereby learning how our workflow operates. This may also help reduce
> > the review burden on our friendly maintainers.
> >
> > I would like to try this kind of periodic report as an experimental
> > effort, with its frequency adjusted according to the size of the patch
> > backlog and the level of activity on the mailing list. What do you
> > think? Please feel free to make comments.
> 
> I think this is fine since linux-doc or narrowly zh_CN/TW do not have
> many volumes of patches per day.

Exactly. I think Junio C Hamano has a script to do this automaticly, but
I did this manually because our volumes is not that high as Git.

> > By the way, I borrowed the subject line directly from Git's "What's
> > cooking in git.git". Does anyone have a better suggestion for the name? ;-)
> 
> fine with this title

OK, let's keep it now.

Re: What's cooking in zh_CN (Jul 2026)

[Dongliang Mu]

On 7/14/26 5:51 PM, Weijie Yuan wrote:
> On Tue, Jul 14, 2026 at 05:32:12PM +0800, Dongliang Mu wrote:
>> On Tue, Jul 14, 2026 at 12:51 AM Weijie Yuan <wy@wyuan.org> wrote:
>>> Hi all,
>>>
>>> Since I made many noise these days on the list, which took up a lot of
>>> maintainers' time. This email summarizes the patches for zh_CN that are
>>> currently pending on the mailing list.
>> This is awesome. Maybe we can establish a dashboard for the activities
>> in zh_CN/TW related patches of linux-doc.
>>
>> I personally kept a knowledge base in the IMA (an app for storing
>> knowledge base in the cloud) in our club to monitor these activities.
> I remember kernel.org itself already provides this:
>
>    https://patchwork.kernel.org/
>
> Is this similar to your idea? But I haven't look deep into patchwork
> before.
>
> Of source, having our own thing is definitely okay.


I am not familar with patchwork too. How about Alex?

Dongliang Mu


>>> * Doehyun Baek (2026-07-08) 7 commits
>>>    [PATCH v6 0/7] docs/zh_CN: update DAMON translations
>>>    [PATCH v6 1/7] docs/zh_CN: update DAMON design translation
>>>    [PATCH v6 2/7] docs/zh_CN: add DAMON_STAT usage translation
>>>    [PATCH v6 3/7] docs/zh_CN: update DAMON index translation
>>>    [PATCH v6 4/7] docs/zh_CN: update DAMON start translation
>>>    [PATCH v6 5/7] docs/zh_CN: update DAMON usage translation
>>>    [PATCH v6 6/7] docs/zh_CN: update DAMON reclaim translation
>>>    [PATCH v6 7/7] docs/zh_CN: update DAMON LRU sort translation
>> Maybe I can take a review tomorrow.
> No rush of course ;-)
>
>>> Okay, I have checked the 200 most recent messages on the mailing list,
>>> going back to 15:09 UTC on February 25, 2026. If I have missed anything,
>>> or I made a mistake somewhere, please let me know.
>>>
>>> As you may have noticed, I borrowed (stole) this idea from Junio C
>>> Hamano. Sending this kind of message, somewhat like a weekly status
>>> report, not only helps maintainers keep track of outstanding work, but
>>> also lets contributors know the current status of their patches.
>> As mentioned before, can we have a dashboard to see the status of
>> patches in zh_CN/TW? This is more useful in my mind.
>>
>>> More importantly, it gives newcomers an overview of the current state of
>>> the project. New contributors can begin not only by submitting patches,
>>> but also by reviewing patches already posted to the mailing list,
>>> thereby learning how our workflow operates. This may also help reduce
>>> the review burden on our friendly maintainers.
>>>
>>> I would like to try this kind of periodic report as an experimental
>>> effort, with its frequency adjusted according to the size of the patch
>>> backlog and the level of activity on the mailing list. What do you
>>> think? Please feel free to make comments.
>> I think this is fine since linux-doc or narrowly zh_CN/TW do not have
>> many volumes of patches per day.
> Exactly. I think Junio C Hamano has a script to do this automaticly, but
> I did this manually because our volumes is not that high as Git.
>
>>> By the way, I borrowed the subject line directly from Git's "What's
>>> cooking in git.git". Does anyone have a better suggestion for the name? ;-)
>> fine with this title
> OK, let's keep it now.

Re: What's cooking in zh_CN (Jul 2026)

[Alex Shi]

On 2026/7/14 17:54, Dongliang Mu wrote:
>>>> Since I made many noise these days on the list, which took up a lot of
>>>> maintainers' time. This email summarizes the patches for zh_CN that are
>>>> currently pending on the mailing list.
>>> This is awesome. Maybe we can establish a dashboard for the activities
>>> in zh_CN/TW related patches of linux-doc.
>>>
>>> I personally kept a knowledge base in the IMA (an app for storing
>>> knowledge base in the cloud) in our club to monitor these activities.
>> I remember kernel.org itself already provides this:
>>
>> https://patchwork.kernel.org/
>>
>> Is this similar to your idea? But I haven't look deep into patchwork
>> before.
>>
>> Of source, having our own thing is definitely okay.
> 
> 
> I am not familar with patchwork too. How about Alex?

I don't know if the patchwork has a similar feature like this email, 
does it?

Thanks!

Re: What's cooking in zh_CN (Jul 2026)

[Weijie Yuan]

I took a look about patchwork, it is basically like a mailing-list
version issue tracker / pull-request dashboard.

It can manage patch backlog, assign patches, record CI results, and mark
patches as accepted, rejected, superseded, or under review. and record
trailers. Well, pretty much like a mini version of Gerrit or SourceHut.

But I think it's a little complicated for our needs, as it offers many
features that we might not actually need, which involves learning costs
and maintenance costs.

Just now, while going through patchwork of other lists a bit, I didn't
seem to find a way to filter out Chinese patches from the linux-doc
list, if we were to use it.

Dongliang, is the dashboard you want exactly like the one I sent in this
email, which is read-only? Or perhaps wish there are other functions as
well. For example, you can mark the patch series you have reviewed.

I can't find what IMA is btw.

[1] An exmaple of marking status of a patch in SourceHut
    https://lists.sr.ht/~sircmpwn/sr.ht-dev/patches/70509