From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zytor.com (terminus.zytor.com [198.137.202.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7654A3624B0 for ; Mon, 23 Mar 2026 20:32:10 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.136 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774297931; cv=none; b=p+MLSUDXVNsLNcgISBDANQhNY4pVsHqYT2AWtiK87m0Gm6/qvZMBaxLj0KVlit32iix7/mA//JAoJ53Z2sZ2+ZXkiMJsSMKllTT26VhrZyXHAsY5h8dPbQ/uTRe6Jzi0gBLYwLaZMnfdt3VgQPOQNhJSTUAuV8sK/x1zZqNwcac= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774297931; c=relaxed/simple; bh=dl5fLUi+QyzsR8JUGnbDc0wqJeC7IG8TujZVYx0iXSA=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=DaAQbQnqeKN56E80SvWoDb3rJIsI3eiQMUX57MRX4JaI6K6MGbdBKuR2Tq3aSzvHGYMlBTcAXEbnFaWGAKxEz/Ivcg3xKgzEfnTnuq/mNxelI1J9BWq7yZjpYsHFJCqmrp0MT0SxJu+56Nwvc+iZuX3czYNMPPR1vIqxhDxR6kA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com; spf=pass smtp.mailfrom=zytor.com; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b=Onwdk5EH; arc=none smtp.client-ip=198.137.202.136 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=zytor.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zytor.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=zytor.com header.i=@zytor.com header.b="Onwdk5EH" Received: from mail.zytor.com (c-76-133-66-138.hsd1.ca.comcast.net [76.133.66.138]) (authenticated bits=0) by mail.zytor.com (8.18.1/8.17.1) with ESMTPSA id 62NKFZsE3117893 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 23 Mar 2026 13:15:43 -0700 DKIM-Filter: OpenDKIM Filter v2.11.0 mail.zytor.com 62NKFZsE3117893 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zytor.com; s=2026022301; t=1774296943; bh=EPn0TwMqh67fwpN1tu3gkpmogXCxSXiEVNcqMGKGqJg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Onwdk5EHWCKzReZqJZHteVI4sIGvbNWCC3VD9Z6ZXJVjTixNRDiM5Nlx+hwDzqaZ+ RkNZx6XmFM8AmWP8zNY3Vze+hFL7XifH+o/a2/4MGWn0P0ZzQvJhPzoroLNXz10EFt M9Sf8QMM5683dXD0KcMOQkHeAx3OOyPVrlhyJDhuEJ/74HANNKdWNhqcGLF+PN0OwP cgEVu2UY30qYEJMdHunPmOdcqJ4cw3lty8Hf0HhBZjGG7OwBAJtyxE6C6KnTqwT5c0 A2jpPnwAYHgn2vL4ndI7WEZVd/HuJhAbNsk5bH2pr7ez9kWGc6mKZaeazoewsVDnaX gR4smVHd/X66w== From: "H. Peter Anvin" To: Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" Cc: "Peter Zijlstra (Intel)" , Kees Cook , Xin Li , "Ahmed S. Darwish" , Sohil Mehta , linux-kernel@vger.kernel.org Subject: [PATCH 2/2] x86/Kconfig: tighten up wording of the CONFIG_X86_FRED help text Date: Mon, 23 Mar 2026 13:15:05 -0700 Message-ID: <20260323201510.1537333-3-hpa@zytor.com> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260323201510.1537333-1-hpa@zytor.com> References: <20260323201510.1537333-1-hpa@zytor.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit The CONFIG_X86_FRED help text has both "try to" and "if the system supports it", which are redundant statements. Remove "try to". Signed-off-by: H. Peter Anvin (Intel) --- arch/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index e2df1b147184..876b663dcf38 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -557,7 +557,7 @@ config X86_FRED bool "Flexible Return and Event Delivery" depends on X86_64 help - When enabled, try to use Flexible Return and Event Delivery + When enabled, 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 it. -- 2.53.0