[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7917018190d71e6ebecd91ce81f5f2c@vaga.pv.it>
Date: Wed, 07 Feb 2024 18:06:11 +0100
From: Federico Vaga <federico.vaga@...a.pv.it>
To: Lukas Bulwahn <lukas.bulwahn@...il.com>
Cc: Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] doc:it_IT: fix a typo in the config name in RCU torture
Thank you for the fix
On 2024-02-07 16:03, Lukas Bulwahn wrote:
> 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.
>
> Per esempio, potreste usare questo script::
--
Federico Vaga
Powered by blists - more mailing lists