[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87mssafuef.fsf@meer.lwn.net>
Date: Thu, 08 Feb 2024 15:44:40 -0700
From: Jonathan Corbet <corbet@....net>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>, Federico Vaga
<federico.vaga@...a.pv.it>, linux-doc@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org, Lukas
Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: [PATCH] doc:it_IT: fix a typo in the config name in RCU torture
Lukas Bulwahn <lukas.bulwahn@...il.com> writes:
> This issue was detected with the scripts/checkkconfigsymbols.py tool.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@...il.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.
Applied, grazie,
jon
Powered by blists - more mailing lists