From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Federico Vaga <federico.vaga@vaga.pv.it>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] doc:it_IT: fix a typo in the config name in RCU torture
Date: Wed, 7 Feb 2024 16:03:22 +0100 [thread overview]
Message-ID: <20240207150322.20238-1-lukas.bulwahn@gmail.com> (raw)
This issue was detected with the scripts/checkkconfigsymbols.py tool.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
Documentation/translations/it_IT/RCU/torture.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/translations/it_IT/RCU/torture.rst b/Documentation/translations/it_IT/RCU/torture.rst
index 79d9e6932acc..189f7c6caebc 100644
--- a/Documentation/translations/it_IT/RCU/torture.rst
+++ b/Documentation/translations/it_IT/RCU/torture.rst
@@ -129,7 +129,7 @@ Uso su specifici kernel
A volte può essere utile eseguire RCU torture su un kernel già compilato, ad
esempio quando lo si sta per mettere in proeduzione. In questo caso, il kernel
-dev'essere compilato con CONFIG_RCU_TORTUE_TEST=m, cosicché le verifiche possano
+dev'essere compilato con CONFIG_RCU_TORTURE_TEST=m, cosicché le verifiche possano
essere avviate usano modprobe e terminate con rmmod.
Per esempio, potreste usare questo script::
--
2.17.1
next reply other threads:[~2024-02-07 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 15:03 Lukas Bulwahn [this message]
2024-02-07 17:06 ` [PATCH] doc:it_IT: fix a typo in the config name in RCU torture Federico Vaga
2024-02-08 22:44 ` 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=20240207150322.20238-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=corbet@lwn.net \
--cc=federico.vaga@vaga.pv.it \
--cc=kernel-janitors@vger.kernel.org \
--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