mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/fred for v7.1-rc1
Date: Mon, 13 Apr 2026 21:44:44 +0200	[thread overview]
Message-ID: <20260413194444.GAad1HrCe2ScYYET2l@fat_crate.local> (raw)

Hi Linus,

please pull the x86 FRED lineup for v7.1-rc1.

Thx.

---

The following changes since commit c369299895a591d96745d6492d4888259b004a9e:

  Linux 7.0-rc5 (2026-03-22 14:42:17 -0700)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/x86_fred_for_v7.1_rc1

for you to fetch changes up to f0958d588e6de263224ca92087b45ce72fa25c91:

  x86/fred: Remove kernel log message when initializing exceptions (2026-03-27 16:38:24 +0100)

----------------------------------------------------------------
- We made the FRED support an opt-in initially out of fear of it breaking
  machines left and right in the case of a hw bug in the first generation of
  machines supporting it. Now that that the FRED code has seen a lot of
  hammering, flip the logic to be opt-out as is the usual case with new hw
  features

----------------------------------------------------------------
H. Peter Anvin (1):
      x86/fred: Enable FRED by default

Sohil Mehta (1):
      x86/fred: Remove kernel log message when initializing exceptions

 Documentation/admin-guide/kernel-parameters.txt | 4 ++--
 arch/x86/Kconfig                                | 2 +-
 arch/x86/kernel/cpu/common.c                    | 2 +-
 arch/x86/kernel/fred.c                          | 3 ---
 4 files changed, 4 insertions(+), 7 deletions(-)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2026-04-13 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 19:44 Borislav Petkov [this message]
2026-04-14 22:48 ` pr-tracker-bot

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=20260413194444.GAad1HrCe2ScYYET2l@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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®