[PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

[PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

[wpeterYY]

From: Yikun Wei <wpeterYY@outlook.com>
Date: Sat, 17 Oct 2026 19:54:43 +0800
Subject: [PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

The fault-injection documentation has been on the TODO list of the
Chinese documentation index for a long time. This series translates
the whole fault-injection directory into Chinese:

- fault-injection/index.rst
- fault-injection/fault-injection.rst
- fault-injection/notifier-error-inject.rst
- fault-injection/nvme-fault-injection.rst
- fault-injection/provoke-crashes.rst

The first patch also references the new index in the top-level
Chinese index and drops the corresponding TODO list entry.

All translations follow the Chinese translation specification in
Documentation/translations/zh_CN/how-to.rst, and the command lines
and outputs in the examples are kept verbatim.

v1->v2:
  - Resubmit the series with clean, standalone patch emails; the
    first submission was sent through a webmail client and the
    patch bodies were broken by quoted text. Thanks Dongliang Mu
    for pointing this out. No changes to the patch contents.

Yikun Wei (5):
  docs/zh_CN: add fault-injection index Chinese translation
  docs/zh_CN: add fault-injection Chinese translation
  docs/zh_CN: add notifier-error-inject Chinese translation
  docs/zh_CN: add nvme-fault-injection Chinese translation
  docs/zh_CN: add provoke-crashes Chinese translation

 .../zh_CN/fault-injection/fault-injection.rst | 620 ++++++++++++++++++
 .../zh_CN/fault-injection/index.rst           |  20 +
 .../fault-injection/notifier-error-inject.rst | 107 +++
 .../fault-injection/nvme-fault-injection.rst  | 185 ++++++
 .../zh_CN/fault-injection/provoke-crashes.rst |  62 ++
 Documentation/translations/zh_CN/index.rst    |   2 +-
 6 files changed, 995 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/translations/zh_CN/fault-injection/fault-injection.rst
 create mode 100644 Documentation/translations/zh_CN/fault-injection/index.rst
 create mode 100644 Documentation/translations/zh_CN/fault-injection/notifier-error-inject.rst
 create mode 100644 Documentation/translations/zh_CN/fault-injection/nvme-fault-injection.rst
 create mode 100644 Documentation/translations/zh_CN/fault-injection/provoke-crashes.rst

--
2.43.0

[PATCH v2 1/5] docs/zh_CN: add fault-injection index Chinese translation

[wpeterYY]

From: Yikun Wei <wpeterYY@outlook.com>
Date: Sat, 17 Oct 2026 19:50:27 +0800
Subject: [PATCH v2 1/5] docs/zh_CN: add fault-injection index Chinese translation

Translate Documentation/fault-injection/index.rst into Chinese.

Update the translation through commit a592a36e4937
("Documentation: use a source-read extension for the index link boilerplate")

Signed-off-by: Yikun Wei <wpeterYY@outlook.com>
---
 .../zh_CN/fault-injection/index.rst           | 20 +++++++++++++++++++
 Documentation/translations/zh_CN/index.rst    |  2 +-
 2 files changed, 21 insertions(+), 1 deletion(-)
 create mode 100644 Documentation/translations/zh_CN/fault-injection/index.rst

diff --git a/Documentation/translations/zh_CN/fault-injection/index.rst b/Documentation/translations/zh_CN/fault-injection/index.rst
new file mode 100644
index 000000000000..1b3c0c8e5ebb
--- /dev/null
+++ b/Documentation/translations/zh_CN/fault-injection/index.rst
@@ -0,0 +1,20 @@
+.. SPDX-License-Identifier: GPL-2.0
+.. include:: ../disclaimer-zh_CN.rst
+
+:Original: Documentation/fault-injection/index.rst
+
+:翻译:
+
+ Yikun Wei <wpeterYY@outlook.com>
+
+========
+故障注入
+========
+
+.. toctree::
+    :maxdepth: 1
+
+    fault-injection
+    notifier-error-inject
+    nvme-fault-injection
+    provoke-crashes
diff --git a/Documentation/translations/zh_CN/index.rst b/Documentation/translations/zh_CN/index.rst
index b08c09d8e96e..075fe15f06fb 100644
--- a/Documentation/translations/zh_CN/index.rst
+++ b/Documentation/translations/zh_CN/index.rst
@@ -74,12 +74,12 @@
    dev-tools/index
    dev-tools/testing-overview
    kernel-hacking/index
+   fault-injection/index
    rust/index

 TODOList:

 * trace/index
-* fault-injection/index
 * livepatch

 面向用户的文档
--
2.43.0

回复: [PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

[wpeterYY]

Hi Alex and all,

A quick note on the submission format: my email provider (outlook.com)
has SMTP/IMAP client authentication disabled, so I can only send mail
through the webmail interface, and changing the subject line of a
reply detaches it from the original thread. As a result, the patches
in this series appear as separate emails instead of a single thread.

The patches are numbered [PATCH v2 1/5] through [PATCH v2 5/5] and
should be applied in that order on top of the docs-next tree. If you
would prefer a different format, please let me know and I will
resend.

Sorry for the inconvenience, and thanks for your work on the Chinese
documentation.

Yikun Wei

Re: 回复: [PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

[Weijie Yuan]

On Sun, Oct 18, 2026 at 02:10:52AM +0000, wpeterYY@outlook.com wrote:
> Hi Alex and all,
> 
> A quick note on the submission format: my email provider (outlook.com)
> has SMTP/IMAP client authentication disabled, so I can only send mail
> through the webmail interface, and changing the subject line of a
> reply detaches it from the original thread. As a result, the patches
> in this series appear as separate emails instead of a single thread.

Aha, I remember that back to 2016 in Kernel Recipes 2016 - Patches
carved into stone tablets… by Greg KH, he said that Exchange and Outlook
are known to corrupt patches. I don't know if we can do it or how to do
it now, a decade later. ;-) Because I do remember recently I saw a patch
is sent with outlook.com and seems to be able to be applied cleanly.

Here comes the interesting part:

# on Jon's docs-mw branch
$ b4 shazam 'https://lore.kernel.org/linux-doc/SI2PPFCA6543649A0CB710CDA1CA17757DDDD992@SI2PPFCA6543649.apcprd04.prod.outlook.com/'
Looking up SI2PPFCA6543649A0CB710CDA1CA17757DDDD992@SI2PPFCA6543649.apcprd04.prod.outlook.com
Checking for newer revisions
Grabbing search results from lore.kernel.org
Analyzing 3 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 0 code-review messages
Checking attestation on all messages, may take a moment...
---
  ✓ [PATCH v2 1/5] docs/zh_CN: add fault-injection index Chinese translation
    ✓ Signed: DKIM/outlook.com
  ERROR: missing [2/5]!
  ERROR: missing [3/5]!
  ERROR: missing [4/5]!
  ERROR: missing [5/5]!
---
Total patches: 1
---
WARNING: Thread incomplete!
Applying: docs/zh_CN: add fault-injection index Chinese translation
Patch failed at 0001 docs/zh_CN: add fault-injection index Chinese translation
error: patch failed: Documentation/translations/zh_CN/index.rst:74
error: Documentation/translations/zh_CN/index.rst: patch does not apply
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"

# i.e. [1/5] can not be applied successfully.

$ git am --abort

$ b4 shazam 'https://lore.kernel.org/linux-doc/SI2PPFCA6543649423BA7595B9B6BF31774DD992@SI2PPFCA6543649.apcprd04.prod.outlook.com/'
Looking up SI2PPFCA6543649423BA7595B9B6BF31774DD992@SI2PPFCA6543649.apcprd04.prod.outlook.com
Analyzing 1 messages in the thread
Looking for additional code-review trailers on lore.kernel.org
Analyzing 8 code-review messages
Checking attestation on all messages, may take a moment...
---
  ERROR: missing [1/5]!
  ✓ [PATCH v2 2/5] docs/zh_CN: add fault-injection Chinese translation
    ✓ Signed: DKIM/outlook.com
  ERROR: missing [3/5]!
  ERROR: missing [4/5]!
  ERROR: missing [5/5]!
---
Total patches: 1
---
WARNING: Thread incomplete!
Applying: docs/zh_CN: add fault-injection Chinese translation

# i.e. [2/5] can be applied successfully on top of Jon's docs-mw branch.

Perhaps I need to see if there's anything I did wrong.

Thanks.

回复: 回复: [PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

[wpeterYY]

Hi,

Thanks a lot for testing the series with b4 ― that was very helpful.

To clarify two points:

1) The "missing [2/5]..[5/5]" warnings are because the patches were
   sent as separate (unthreaded) emails, so b4 can only assemble the
   full series when pointed at the cover-letter URL. I'll resend v3
   properly threaded so a single `b4 shazam <cover-url>` grabs all 5.

2) The [1/5] failure is a real base-drift issue: I generated the series
   against an older index.rst, and docs-mw has since changed. The patch
   content itself is intact (DKIM signed, and [2/5] applied cleanly on
   your tree), so it's not an Outlook corruption problem.

I'll rebase onto docs-mw and resend as v3 shortly.

Thanks,
Yikun

Re: 回复: 回复: [PATCH v2 0/5] docs/zh_CN: add fault-injection Chinese translations

[Weijie Yuan]

Hi,

On Tue, Oct 20, 2026 at 11:40:54AM +0000, wpeterYY@outlook.com wrote:
> Hi,
> 
> Thanks a lot for testing the series with b4 - that was very helpful.
> 
> To clarify two points:
> 
> 1) The "missing [2/5]..[5/5]" warnings are because the patches were
>    sent as separate (unthreaded) emails, so b4 can only assemble the
>    full series when pointed at the cover-letter URL. I'll resend v3
>    properly threaded so a single `b4 shazam <cover-url>` grabs all 5.

Yes. I saw your explanation below.

> 
> 2) The [1/5] failure is a real base-drift issue: I generated the series
>    against an older index.rst, and docs-mw has since changed. The patch
>    content itself is intact (DKIM signed, and [2/5] applied cleanly on
>    your tree), so it's not an Outlook corruption problem.

Oh, I should have taken the time to take a look carefully first, because
I originally thought there were no conflicts in the modified content
between the two branches.

> I'll rebase onto docs-mw and resend as v3 shortly.

Ah, sorry for misleading. I used docs-mw is just because I happened to
be on that branch. But actually we want to make our work based on Alex's
docs-next branch.

Thanks for your reply!