All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: peterz@infradead.org, tglx@linutronix.de, x86@kernel.org
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org
Subject: [PATCH 0/1 v2] x86/cpu: Add INTEL_LUNARLAKE_M to X86_BUG_MONITOR
Date: Tue, 12 Nov 2024 00:28:25 -0500	[thread overview]
Message-ID: <20241112053722.356303-1-lenb@kernel.org> (raw)
In-Reply-To: <20241111162316.GH22801@noisy.programming.kicks-ass.net>

It was folly to respond to review feedback by attempting to add bits
to the kexec path to this simple patch.  So that misguided hunk is removed.

Here is the 1-line patch that addresses the problem that users see
in the field today.

If kexec proves to be an issue on LNL, that can be addressed
in a subsequent patch.

thanks,
-Len


  parent reply	other threads:[~2024-11-12  5:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-08 13:49 [PATCh 0/2] Add Intel Lunarlake to X86_BUG_MONITOR Len Brown
2024-11-08 13:49 ` [PATCH backport to 6.10] x86/cpu: Add INTEL_FAM6_LUNARLAKE_M " Len Brown
2024-11-08 13:53   ` kernel test robot
2024-11-12  1:07   ` Thomas Gleixner
2024-11-08 13:49 ` [PATCH] x86/cpu: Add INTEL_LUNARLAKE_M " Len Brown
2024-11-08 14:34   ` Rafael J. Wysocki
2024-11-11 16:23   ` Peter Zijlstra
2024-11-12  0:27     ` Thomas Gleixner
2024-11-12  5:28     ` Len Brown [this message]
2024-11-12  5:28       ` [PATCH 1/1] " Len Brown
2024-11-12 11:44         ` Rafael J. Wysocki
     [not found]           ` <CAJvTdKnRpDQKUVNJ4Gp7r+WaHo0y-Wume3ay7toHU+Xz0gv2Zw@mail.gmail.com>
2024-11-12 13:14             ` Rafael J. Wysocki
     [not found]               ` <CAJvTdK=SnRqwjR5fUatP0CzaXD_CpZ-1cc+2yX0D8_XM_3oJUw@mail.gmail.com>
2024-11-12 15:02                 ` Rafael J. Wysocki
2024-11-11 20:20   ` [PATCH] " Thomas Gleixner

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=20241112053722.356303-1-lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.