linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yanteng Si <siyanteng@loongson.cn>
To: corbet@lwn.net, alexs@kernel.org, bobwxc@email.cn, seakeel@gmail.com
Cc: Yanteng Si <siyanteng@loongson.cn>,
	chenhuacai@kernel.org, jiaxun.yang@flygoat.com,
	linux-doc@vger.kernel.org, siyanteng01@gmail.com,
	zhoubinbin@loongson.cn
Subject: [PATCH 0/3] docs/zh_CN: Update the translation of vm to 5.19-rc1
Date: Thu,  9 Jun 2022 21:27:17 +0800	[thread overview]
Message-ID: <cover.1654780922.git.siyanteng@loongson.cn> (raw)

Update .../zh_CN/vm/* to 5.19-rc1.

Yanteng Si (3):
  docs/zh_CN: Update the translation of highmem to 5.19-rc1
  docs/zh_CN: Update the translation of page_owner to 5.19-rc1
  docs/zh_CN: Update the translation of vm index to 5.19-rc1

 .../translations/zh_CN/vm/bootmem.rst         | 13 ++++
 .../translations/zh_CN/vm/highmem.rst         | 77 +++++++++++--------
 Documentation/translations/zh_CN/vm/index.rst | 39 ++++++++--
 Documentation/translations/zh_CN/vm/oom.rst   | 13 ++++
 .../translations/zh_CN/vm/page_allocation.rst | 13 ++++
 .../translations/zh_CN/vm/page_cache.rst      | 13 ++++
 .../translations/zh_CN/vm/page_owner.rst      | 70 +++++++++++++++--
 .../translations/zh_CN/vm/page_reclaim.rst    | 13 ++++
 .../translations/zh_CN/vm/page_tables.rst     | 13 ++++
 .../translations/zh_CN/vm/physical_memory.rst | 13 ++++
 .../translations/zh_CN/vm/process_addrs.rst   | 13 ++++
 Documentation/translations/zh_CN/vm/shmfs.rst | 13 ++++
 Documentation/translations/zh_CN/vm/swap.rst  | 13 ++++
 .../translations/zh_CN/vm/vmalloc.rst         | 13 ++++
 14 files changed, 282 insertions(+), 47 deletions(-)
 create mode 100644 Documentation/translations/zh_CN/vm/bootmem.rst
 create mode 100644 Documentation/translations/zh_CN/vm/oom.rst
 create mode 100644 Documentation/translations/zh_CN/vm/page_allocation.rst
 create mode 100644 Documentation/translations/zh_CN/vm/page_cache.rst
 create mode 100644 Documentation/translations/zh_CN/vm/page_reclaim.rst
 create mode 100644 Documentation/translations/zh_CN/vm/page_tables.rst
 create mode 100644 Documentation/translations/zh_CN/vm/physical_memory.rst
 create mode 100644 Documentation/translations/zh_CN/vm/process_addrs.rst
 create mode 100644 Documentation/translations/zh_CN/vm/shmfs.rst
 create mode 100644 Documentation/translations/zh_CN/vm/swap.rst
 create mode 100644 Documentation/translations/zh_CN/vm/vmalloc.rst

-- 
2.27.0


             reply	other threads:[~2022-06-09 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 13:27 Yanteng Si [this message]
2022-06-09 13:27 ` [PATCH 1/3] docs/zh_CN: Update the translation of highmem to 5.19-rc1 Yanteng Si
2022-06-09 17:09   ` Wu X.C.
2022-06-13  2:14     ` Yanteng Si
2022-06-13  6:17       ` Alex Shi
2022-06-09 13:27 ` [PATCH 2/3] docs/zh_CN: Update the translation of page_owner " Yanteng Si
2022-06-09 17:09   ` Wu X.C.
2022-06-13  2:33     ` Yanteng Si
2022-06-09 13:27 ` [PATCH 3/3] docs/zh_CN: Update the translation of vm index " Yanteng Si
2022-06-10 16:12   ` Wu X.C.
2022-06-13  2:38     ` Yanteng Si

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=cover.1654780922.git.siyanteng@loongson.cn \
    --to=siyanteng@loongson.cn \
    --cc=alexs@kernel.org \
    --cc=bobwxc@email.cn \
    --cc=chenhuacai@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=seakeel@gmail.com \
    --cc=siyanteng01@gmail.com \
    --cc=zhoubinbin@loongson.cn \
    /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;
as well as URLs for NNTP newsgroup(s).