Re: [PATCH] docs/zh_CN: Update arch/riscv/vm-layout.rst translation

[Yao Zi <me@ziyao.cc>]

On Sun, Aug 30, 2026 at 10:32:13PM +0800, Weijie Yuan wrote:
> On Sat, Aug 29, 2026 at 04:57:49PM +0000, Yao Zi wrote:
> > On Sat, Aug 29, 2026 at 12:15:10PM +0800, Yukai Wu wrote:
> > > Update Documentation/arch/riscv/vm-layout.rst translation.
> > > 
> > > Update the translation through commit 954260ff5a46
> > > ("Revert "RISC-V: mm: Document mmap changes"")
> > > 
> > > Signed-off-by: Yukai Wu <xiaoyewuz.Ruster@gmail.com>
> > > ---
> > >  .../zh_CN/arch/riscv/vm-layout.rst             | 18 +++++++++---------
> > >  1 file changed, 9 insertions(+), 9 deletions(-)
> > > 
> > > diff --git a/Documentation/translations/zh_CN/arch/riscv/vm-layout.rst b/Documentation/translations/zh_CN/arch/riscv/vm-layout.rst
> > > index 4b9f4dcf6c19..0d0ec8ea5d05 100644
> > > --- a/Documentation/translations/zh_CN/arch/riscv/vm-layout.rst
> > > +++ b/Documentation/translations/zh_CN/arch/riscv/vm-layout.rst
> > > @@ -15,7 +15,7 @@ RISC-V Linux上的虚拟内存布局
> > >  :作者: Alexandre Ghiti <alex@ghiti.fr>
> > >  :日期: 12 February 2021
> > >  
> > > -这份文件描述了RISC-V Linux内核使用的虚拟内存布局。
> > > +这份文件描述了 RISC-V Linux 内核使用的虚拟内存布局。
> > >  
> > >  32位 RISC-V Linux 内核
> > >  ======================
> > > @@ -28,9 +28,9 @@ TODO
> > >  64位 RISC-V Linux 内核
> > >  ======================
> > >  
> > > -RISC-V特权架构文档指出，64位地址 "必须使第63-48位值都等于第47位，否则将发生缺页异常。"：这将虚
> > > -拟地址空间分成两半，中间有一个非常大的洞，下半部分是用户空间所在的地方，上半部分是RISC-V Linux
> > > -内核所在的地方。
> > > +RISC-V 特权架构文档指出，64 位地址“必须使第 63-48 位值都等于第 47 位，否则将发生缺页异常。”：
> > > +这将虚拟地址空间分成两半，中间有一个非常大的洞，下半部分是用户空间所在的地方，上半部分是 RISC-V
> > > +Linux 内核所在的地方。
> > 
> > I think changes above are purely style improvements? If so please
> > mention it in the commit message, instead of specifying it's "updating"
> > only.
> 
> Agreed. To put it further, I think the commit message template we
> provided in how-to.rst [1] is somewhat like telling contributors: That's
> all you need to do.

Oops, I don't even realize it's part of our existing contributing
guide...

> Of course, in some cases, the patch is quite simple and there is nothing
> else to elaborate on. However, in some cases, such as when making
> extensive changes and updates, we should encourage contributors to write
> down some relevant information for future reference.
> 
> Similarly, just like this patch, the author did more than just update;
> he also carried out other actions, but failed to include the relevant
> details in the commit message. So I feel that perhaps our template might
> have somewhat restricted our writing? (to some extent)

Agree.

> Sure, the requirements for commit messages in the Chinese documentation
> are certainly not as strict as those for the more core subsystems.
> However, I do think it's fine to appropriately explicitly encourage
> contributors to include more meaningful relevant information in the
> commit messages.
> 
> Any ideas for this, or any objections? ;)

I think it's worth pointing out that the template commit message is for
reference only in how-to.rst, and guiding readers to
submitting-patches.rst so at least newcomers have a brief understanding
of the process and requirements.

Now how-to.rst refers process/index.rst, but this index seems to contain
too much for anyone unfamiliar with the process to read through.

> Thanks!
> 
> [1] https://docs.kernel.org/translations/zh_CN/how-to.html#id13

Regards,
Yao Zi

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv