From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"Alexander A. Klimov" <grandmaster@al2klimov.de>,
Alex Shi <alexs@kernel.org>, Wu XiangCheng <bobwxc@email.cn>,
linux-kernel@vger.kernel.org
Subject: [PATCH 03/10] docs: translations/zh_CN: fix a typo at 8.Conclusion.rst
Date: Wed, 19 May 2021 10:51:40 +0200 [thread overview]
Message-ID: <40b3d5c983fb06d8a58d1f613c175a98e0631677.1621413933.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1621413933.git.mchehab+huawei@kernel.org>
transaltions -> translations
Acked-by: Wu XiangCheng <bobwxc@email.cn>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/translations/zh_CN/process/8.Conclusion.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/zh_CN/process/8.Conclusion.rst b/Documentation/translations/zh_CN/process/8.Conclusion.rst
index 71c3e30efc6f..4707f0101964 100644
--- a/Documentation/translations/zh_CN/process/8.Conclusion.rst
+++ b/Documentation/translations/zh_CN/process/8.Conclusion.rst
@@ -19,7 +19,7 @@
:ref:`Documentation/translations/zh_CN/process/howto.rst <cn_process_howto>`
文件是一个重要的起点;
:ref:`Documentation/translations/zh_CN/process/submitting-patches.rst <cn_submittingpatches>`
-和 :ref:`Documentation/transaltions/zh_CN/process/submitting-drivers.rst <cn_submittingdrivers>`
+和 :ref:`Documentation/translations/zh_CN/process/submitting-drivers.rst <cn_submittingdrivers>`
也是所有内核开发人员都应该阅读的内容。许多内部内核API都是使用kerneldoc机制
记录的;“make htmldocs”或“make pdfdocs”可用于以HTML或PDF格式生成这些文档
(尽管某些发行版提供的tex版本会遇到内部限制,无法正确处理文档)。
--
2.31.1
next prev parent reply other threads:[~2021-05-19 8:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 8:51 [PATCH 00/10] Documentation build warning fixes Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 01/10] docs: update sysfs-platform_profile.rst reference Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 02/10] docs: vcpu-requests.rst: fix reference for atomic ops Mauro Carvalho Chehab
2021-05-19 8:51 ` Mauro Carvalho Chehab [this message]
2021-05-19 8:51 ` [PATCH 04/10] docs: sched-bwc.rst: fix a typo on a doc name Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 05/10] docs: update pin-control.rst references Mauro Carvalho Chehab
2021-05-19 10:20 ` Charles Keepax
2021-05-19 14:43 ` Lee Jones
2021-05-25 0:30 ` Linus Walleij
2021-05-19 8:51 ` [PATCH 06/10] docs: virt: api.rst: fix a pointer to SGX documentation Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 07/10] docs: ABI: iommu: remove duplicated definition for sysfs-kernel-iommu_groups Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 08/10] docs: ABI: sysfs-class-backlight: unify ambient light zone nodes Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 09/10] docs: ABI: sysfs-class-led-trigger-pattern: remove repeat duplication Mauro Carvalho Chehab
2021-05-19 8:51 ` [PATCH 10/10] iio: documentation: fix a typo Mauro Carvalho Chehab
2021-05-20 20:08 ` Matthew Wilcox
2021-05-20 20:00 ` [PATCH 00/10] Documentation build warning fixes 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=40b3d5c983fb06d8a58d1f613c175a98e0631677.1621413933.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=alexs@kernel.org \
--cc=bobwxc@email.cn \
--cc=corbet@lwn.net \
--cc=grandmaster@al2klimov.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).