From: LIU Haoyang <tttturtleruss@gmail.com>
To: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: LIU Haoyang <tttturtleruss@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V2] docs/zh_CN: fix an inconsistent statement in dev-tools/testing-overview
Date: Fri, 6 Mar 2026 04:10:58 +0800 [thread overview]
Message-ID: <20260305201100.10119-1-tttturtleruss@gmail.com> (raw)
This patch fixes an inconsistent describtion in testing-overview.rst,
which should be ``kmalloc`` instead of ``kmalloc_arry`` according to
the original text.
Signed-off-by: LIU Haoyang <tttturtleruss@gmail.com>
---
V1 -> V2: fix some typos in the commit message
Documentation/translations/zh_CN/dev-tools/testing-overview.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/zh_CN/dev-tools/testing-overview.rst b/Documentation/translations/zh_CN/dev-tools/testing-overview.rst
index 286ed6b01f65..8bdc51b47b5e 100644
--- a/Documentation/translations/zh_CN/dev-tools/testing-overview.rst
+++ b/Documentation/translations/zh_CN/dev-tools/testing-overview.rst
@@ -154,7 +154,7 @@ Smatch和Coccinelle的强项
Coccinelle可能是最容易写检查的。它在预处理器之前工作，所以用Coccinelle
检查宏中的错误更容易。Coccinelle还能为你创建补丁，这是其他工具无法做到的。
-例如，用Coccinelle你可以从 ``kmalloc_array(x, size, GFP_KERNEL)``
+例如，用Coccinelle你可以从 ``kmalloc(x * size, GFP_KERNEL)``
到 ``kmalloc_array(x, size, GFP_KERNEL)`` 进行大规模转换，这真的很
有用。如果你只是创建一个Smatch警告，并试图把转换的工作推给维护者，他们会很
恼火。你将不得不为每个警告争论是否真的可以溢出。
--
2.53.0
next reply other threads:[~2026-03-05 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 20:10 LIU Haoyang [this message]
2026-03-06 1:29 ` [PATCH V2] docs/zh_CN: fix an inconsistent statement in dev-tools/testing-overview Dongliang Mu
2026-03-07 14:07 ` Alex Shi
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=20260305201100.10119-1-tttturtleruss@gmail.com \
--to=tttturtleruss@gmail.com \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=si.yanteng@linux.dev \
--cc=skhan@linuxfoundation.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