All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>, linux-kernel@vger.kernel.org
Cc: ashok.raj@intel.com, stable-commits@vger.kernel.org
Subject: Re: Patch "x86/smp: Cure kexec() vs. mwait_play_dead() breakage" has been added to the 4.14-stable tree
Date: Wed, 28 Jun 2023 23:34:58 +0200	[thread overview]
Message-ID: <87r0pv2rul.ffs@tglx> (raw)
In-Reply-To: <2023062812-regime-demote-14f8@gregkh>

On Wed, Jun 28 2023 at 21:40, Greg KH wrote:
> On Wed, Jun 28, 2023 at 09:39:09PM +0200, Greg KH wrote:
>> On Wed, Jun 28, 2023 at 09:32:12PM +0200, gregkh@linuxfoundation.org wrote:
>> > 
>> > This is a note to let you know that I've just added the patch titled
>> > 
>> >     x86/smp: Cure kexec() vs. mwait_play_dead() breakage
>> > 
>> > to the 4.14-stable tree which can be found at:
>> >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>> > 
>> > The filename of the patch is:
>> >      x86-smp-cure-kexec-vs.-mwait_play_dead-breakage.patch
>> > and it can be found in the queue-4.14 subdirectory.
>> 
>> Oops, nope, this breaks the build on 4.14.y :(
>
> And on 4.19.y, 5.4.y, 5.10.y, and 5.15.y, so dropped from all of them as
> well.

I'll have a look at it tomorrow.

      reply	other threads:[~2023-06-28 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2023062810-override-roundup-e5bf@gregkh>
2023-06-28 19:39 ` Patch "x86/smp: Cure kexec() vs. mwait_play_dead() breakage" has been added to the 4.14-stable tree Greg KH
2023-06-28 19:40   ` Greg KH
2023-06-28 21:34     ` Thomas Gleixner [this message]

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=87r0pv2rul.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=ashok.raj@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable-commits@vger.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.