From: "H. Peter Anvin" <hpa@zytor.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Xin Li <xin3.li@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/fred: Add missing *it* to Kconfig description
Date: Tue, 12 Mar 2024 09:33:21 -0700 [thread overview]
Message-ID: <bf22db47-2085-44fc-81b6-91f39cd5e4d0@zytor.com> (raw)
In-Reply-To: <20240312161958.102927-2-pmenzel@molgen.mpg.de>
LOL. Major QA failure :)
Acked-by: H. Peter Anvin (Intel) <hpa@zytor.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@molgen.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
next prev parent reply other threads:[~2024-03-12 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 16:19 Paul Menzel
2024-03-12 16:33 ` H. Peter Anvin [this message]
2024-03-22 11:32 ` [tip: x86/cleanups] x86/fred: Fix typo in " tip-bot2 for Paul Menzel
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=bf22db47-2085-44fc-81b6-91f39cd5e4d0@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin3.li@intel.com \
/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
all inboxes | Powered by JetHome®