From: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
sfr@canb.auug.org.au, snovitoll@gmail.com
Subject: [PATCH] Documentation/kasan: fix indentation in translation
Date: Sun, 20 Oct 2024 09:28:13 +0500 [thread overview]
Message-ID: <20241020042813.3223449-1-snovitoll@gmail.com> (raw)
In-Reply-To: <20241016131802.3115788-4-snovitoll@gmail.com>
Fix the warning in linux-next (htmldocs):
> Documentation/translations/zh_TW/dev-tools/kasan.rst:410:
> ERROR: Unexpected indentation.
This is based on -mm tree (linux-mm-unstable branch).
Signed-off-by: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
---
Documentation/translations/zh_TW/dev-tools/kasan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/zh_TW/dev-tools/kasan.rst b/Documentation/translations/zh_TW/dev-tools/kasan.rst
index 35b7fd18a..27fb76451 100644
--- a/Documentation/translations/zh_TW/dev-tools/kasan.rst
+++ b/Documentation/translations/zh_TW/dev-tools/kasan.rst
@@ -407,7 +407,7 @@ KASAN連接到vmap基礎架構以懶清理未使用的影子內存。
所有 KASAN 測試均與 KUnit 測試框架集成，並且可以啟用
透過 ``CONFIG_KASAN_KUNIT_TEST``。可以運行測試並進行部分驗證
- 以幾種不同的方式自動進行；請參閱下面的說明。
+以幾種不同的方式自動進行；請參閱下面的說明。
如果偵測到錯誤，每個 KASAN 測試都會列印多個 KASAN 報告之一。
然後測試列印其編號和狀態。
--
2.34.1
next prev parent reply other threads:[~2024-10-20 4:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 7:16 [PATCH] kasan: migrate copy_user_test to kunit Sabyrzhan Tasbolatov
2024-10-11 9:13 ` Sabyrzhan Tasbolatov
2024-10-12 22:49 ` Andrey Konovalov
2024-10-13 6:33 ` Sabyrzhan Tasbolatov
2024-10-12 22:46 ` Andrey Konovalov
2024-10-13 13:02 ` [PATCH v2 0/3] kasan: migrate the last module test " Sabyrzhan Tasbolatov
2024-10-13 13:02 ` [PATCH v2 1/3] kasan: move checks to do_strncpy_from_user Sabyrzhan Tasbolatov
2024-10-13 16:04 ` Andrey Konovalov
2024-10-13 13:02 ` [PATCH v2 2/3] kasan: migrate copy_user_test to kunit Sabyrzhan Tasbolatov
2024-10-13 16:02 ` Andrey Konovalov
2024-10-13 18:20 ` [PATCH v3 " Sabyrzhan Tasbolatov
2024-10-13 20:25 ` Andrey Konovalov
2024-10-14 2:56 ` [PATCH RESEND v3 0/3] kasan: migrate the last module test " Sabyrzhan Tasbolatov
2024-10-14 2:56 ` [PATCH RESEND v3 1/3] kasan: move checks to do_strncpy_from_user Sabyrzhan Tasbolatov
2024-10-14 2:57 ` [PATCH RESEND v3 2/3] kasan: migrate copy_user_test to kunit Sabyrzhan Tasbolatov
2024-10-14 23:10 ` Andrew Morton
2024-10-15 1:18 ` Andrey Konovalov
2024-10-15 10:53 ` Sabyrzhan Tasbolatov
2024-10-15 23:16 ` Andrey Konovalov
2024-10-16 13:17 ` [PATCH v4 0/3] kasan: migrate the last module test " Sabyrzhan Tasbolatov
2024-10-16 13:18 ` [PATCH v4 1/3] kasan: move checks to do_strncpy_from_user Sabyrzhan Tasbolatov
2024-10-16 13:18 ` [PATCH v4 2/3] kasan: migrate copy_user_test to kunit Sabyrzhan Tasbolatov
2024-10-16 13:18 ` [PATCH v4 3/3] kasan: delete CONFIG_KASAN_MODULE_TEST Sabyrzhan Tasbolatov
2024-10-20 4:28 ` Sabyrzhan Tasbolatov [this message]
2024-10-14 2:57 ` [PATCH RESEND v3 " Sabyrzhan Tasbolatov
2024-10-13 13:02 ` [PATCH v2 " Sabyrzhan Tasbolatov
2024-10-13 16:03 ` Andrey Konovalov
2024-10-13 18:21 ` [PATCH v3 " Sabyrzhan Tasbolatov
2024-10-13 20:25 ` Andrey Konovalov
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=20241020042813.3223449-1-snovitoll@gmail.com \
--to=snovitoll@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®