public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] doc:it_IT: fix a typo in the config name in RCU torture
@ 2024-02-07 15:03 Lukas Bulwahn
  2024-02-07 17:06 ` Federico Vaga
  2024-02-08 22:44 ` Jonathan Corbet
  0 siblings, 2 replies; 3+ messages in thread
From: Lukas Bulwahn @ 2024-02-07 15:03 UTC (permalink / raw)
  To: Federico Vaga, Jonathan Corbet, linux-doc
  Cc: kernel-janitors, linux-kernel, Lukas Bulwahn

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


^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-02-08 22:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-02-07 15:03 [PATCH] doc:it_IT: fix a typo in the config name in RCU torture Lukas Bulwahn
2024-02-07 17:06 ` Federico Vaga
2024-02-08 22:44 ` Jonathan Corbet

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox