linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <seakeel@gmail.com>
To: Tang Yizhou <tangyizhou@huawei.com>,
	siyanteng@loongson.cn, siyanteng01@gmail.com, alexs@kernel.org
Cc: linux-doc@vger.kernel.org, corbet@lwn.net, zhengbin13@huawei.com,
	tangyeechou@gmail.com
Subject: Re: [PATCH v2 1/2] docs/zh_CN: Add locking/index Chinese translation
Date: Sun, 10 Apr 2022 11:50:24 +0800	[thread overview]
Message-ID: <0c37089d-8dc8-8326-322b-e0171dba5736@gmail.com> (raw)
In-Reply-To: <20220408144742.23225-2-tangyizhou@huawei.com>


On 4/8/22 22:47, Tang Yizhou wrote:
> Translate locking/index.rst into Chinese.
>
> Signed-off-by: Tang Yizhou <tangyizhou@huawei.com>


Reviewed-by: Alex Shi <alexs@kernel.org>


> ---
>  Documentation/translations/zh_CN/index.rst    |  2 +-
>  .../translations/zh_CN/locking/index.rst      | 42 +++++++++++++++++++
>  2 files changed, 43 insertions(+), 1 deletion(-)
>  create mode 100644 Documentation/translations/zh_CN/locking/index.rst
>
> diff --git a/Documentation/translations/zh_CN/index.rst b/Documentation/translations/zh_CN/index.rst
> index 88d8df957a78..ac32d8e306ac 100644
> --- a/Documentation/translations/zh_CN/index.rst
> +++ b/Documentation/translations/zh_CN/index.rst
> @@ -108,6 +108,7 @@ TODOList:
>     :maxdepth: 2
>  
>     core-api/index
> +   locking/index
>     accounting/index
>     cpu-freq/index
>     iio/index
> @@ -123,7 +124,6 @@ TODOList:
>  TODOList:
>  
>  * driver-api/index
> -* locking/index
>  * block/index
>  * cdrom/index
>  * ide/index
> diff --git a/Documentation/translations/zh_CN/locking/index.rst b/Documentation/translations/zh_CN/locking/index.rst
> new file mode 100644
> index 000000000000..700df8a2bb70
> --- /dev/null
> +++ b/Documentation/translations/zh_CN/locking/index.rst
> @@ -0,0 +1,42 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +.. include:: ../disclaimer-zh_CN.rst
> +
> +:Original: Documentation/locking/index.rst
> +
> +:翻译:
> +
> +  唐艺舟 Tang Yizhou <tangyeechou@gmail.com>
> +
> +==
> +锁
> +==
> +
> +.. toctree::
> +    :maxdepth: 1
> +
> +TODOList:
> +
> +    * locktypes
> +    * lockdep-design
> +    * lockstat
> +    * locktorture
> +    * mutex-design
> +    * rt-mutex-design
> +    * rt-mutex
> +    * seqlock
> +    * spinlocks
> +    * ww-mutex-design
> +    * preempt-locking
> +    * pi-futex
> +    * futex-requeue-pi
> +    * hwspinlock
> +    * percpu-rw-semaphore
> +    * robust-futexes
> +    * robust-futex-ABI
> +
> +.. only::  subproject and html
> +
> +   Indices
> +   =======
> +
> +   * :ref:`genindex`

  reply	other threads:[~2022-04-10  3:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 14:47 [PATCH v2 0/2] Add spinlocks Chinese translation Tang Yizhou
2022-04-08 14:47 ` [PATCH v2 1/2] docs/zh_CN: Add locking/index " Tang Yizhou
2022-04-10  3:50   ` Alex Shi [this message]
2022-04-13  1:52     ` yanteng si
2022-04-08 14:47 ` [PATCH v2 2/2] docs/zh_CN: Add spinlocks " Tang Yizhou
2022-04-10  3:49   ` Alex Shi
2022-04-13  1:51     ` yanteng si
2022-04-16  8:21 ` [PATCH v2 0/2] " Jonathan Corbet

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=0c37089d-8dc8-8326-322b-e0171dba5736@gmail.com \
    --to=seakeel@gmail.com \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=siyanteng01@gmail.com \
    --cc=siyanteng@loongson.cn \
    --cc=tangyeechou@gmail.com \
    --cc=tangyizhou@huawei.com \
    --cc=zhengbin13@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;
as well as URLs for NNTP newsgroup(s).