[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bf22db47-2085-44fc-81b6-91f39cd5e4d0@zytor.com>
Date: Tue, 12 Mar 2024 09:33:21 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>, Thomas Gleixner
<tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
Xin Li <xin3.li@...el.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/fred: Add missing *it* to Kconfig description
LOL. Major QA failure :)
Acked-by: H. Peter Anvin (Intel) <hpa@...or.com>
Major QA failure there.
On 3/12/24 09:19, Paul Menzel wrote:
> The sentence is incomplete, so add the missing *it*.
>
> Fixes: 2cce95918d63 ("x86/fred: Add Kconfig option for FRED (CONFIG_X86_FRED)")
> Signed-off-by: Paul Menzel <pmenzel@...gen.mpg.de>
> ---
> As a casual user, I wouldn’t know how to figure out, what is required
> from my system to support FRED.
>
> arch/x86/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 8f7271d9f1d7..5fc9fdb84f46 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -504,7 +504,7 @@ config X86_FRED
> When enabled, try to use Flexible Return and Event Delivery
> instead of the legacy SYSCALL/SYSENTER/IDT architecture for
> ring transitions and exception/interrupt handling if the
> - system supports.
> + system supports it.
>
> if X86_32
> config X86_BIGSMP
Powered by blists - more mailing lists