From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: Backport request
Date: Thu, 25 Aug 2022 13:59:46 +0200 [thread overview]
Message-ID: <YwdkMkAPC4tzsoT2@kroah.com> (raw)
In-Reply-To: <1199e064-3311-09cd-283f-d74d5f5c48e3@suse.com>
On Wed, Aug 24, 2022 at 03:52:27PM +0200, Juergen Gross wrote:
> On 24.08.22 14:10, Greg Kroah-Hartman wrote:
> > On Wed, Aug 24, 2022 at 01:20:22PM +0200, Juergen Gross wrote:
> > > Hi Greg,
> > >
> > > stable kernels 5.18 and 5.15 seem to be missing upstream patch
> > > c64cc2802a78 ("x86/entry: Move CLD to the start of the idtentry macro").
> > > This is a prerequisite patch for 64cbd0acb582 ("x86/entry: Don't call
> > > error_entry() for XENPV"), which is included in 5.15.y and 5.18.y.
> > >
> > > Could you please take c64cc2802a78 for 5.15 and 5.18?
> >
> > 5.18 is end-of-life, so that's impossible to do now :(
> >
> > For 5.15.y, the commit does not apply cleanly, can you provide a working
> > backport?
>
> Attached.
Thanks, now queued up.
greg k-h
next prev parent reply other threads:[~2022-08-25 12:00 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 11:20 Backport request Juergen Gross
2022-08-24 12:10 ` Greg Kroah-Hartman
2022-08-24 13:52 ` Juergen Gross
2022-08-25 11:59 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 17:04 Josh Law
2026-04-23 4:55 ` Greg KH
2026-04-23 6:39 ` Krzysztof Kozlowski
2026-04-23 6:46 ` Greg KH
2026-04-23 7:02 ` Krzysztof Kozlowski
2026-04-23 7:56 ` Greg KH
2025-01-18 9:10 backport request Ard Biesheuvel
2025-01-18 9:27 ` Greg KH
2024-11-16 11:08 Backport request Hemdan, Hagar Gamal Halim
2024-11-16 13:51 ` Greg KH
2024-11-12 10:31 Hemdan, Hagar Gamal Halim
2024-11-15 5:10 ` Greg KH
2024-05-29 8:50 backport request Ard Biesheuvel
2024-06-06 13:10 ` Greg KH
2024-06-07 8:43 ` Ard Biesheuvel
2024-06-07 10:23 ` Greg KH
2024-06-07 10:25 ` Ard Biesheuvel
2024-06-07 10:27 ` Ard Biesheuvel
2024-06-07 10:46 ` Greg KH
2024-06-07 10:49 ` Ard Biesheuvel
2024-05-16 10:16 Backport request Hemdan, Hagar Gamal Halim
2024-05-22 15:45 ` Greg KH
2023-08-01 7:17 Hemdan, Hagar Gamal Halim
2023-08-01 7:24 ` Greg KH
2023-07-25 11:13 backport request Ard Biesheuvel
2023-07-25 11:17 ` Ard Biesheuvel
2023-07-25 12:29 ` Greg KH
2023-07-25 12:51 ` Ard Biesheuvel
2023-07-25 13:21 ` Greg KH
2023-07-25 13:25 ` Ard Biesheuvel
2023-07-25 13:41 ` Greg KH
2023-07-25 13:48 ` Ard Biesheuvel
2023-07-27 10:59 ` Greg KH
2020-12-15 16:02 Backport request Daniel Vetter
2020-12-19 12:42 ` Greg KH
2020-12-19 13:56 ` Daniel Vetter
2019-07-16 22:08 Thomas Gleixner
2019-07-16 23:01 ` Greg KH
2019-07-17 23:38 ` Sasha Levin
2019-07-18 7:57 ` Thomas Gleixner
2018-02-28 13:56 Corey Minyard
2018-02-28 14:18 ` Greg KH
2017-03-01 12:31 Juergen Gross
2017-03-21 7:58 ` Juergen Gross
2017-04-05 13:24 ` Ian Jackson
2014-01-13 9:49 Andrew Cooper
2014-01-13 10:47 ` David Vrabel
2014-01-13 11:13 ` Jan Beulich
2014-01-13 11:30 ` David Vrabel
2014-01-13 11:36 ` Jan Beulich
2014-01-13 13:38 ` Daniel Kiper
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=YwdkMkAPC4tzsoT2@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=jiangshanlai@gmail.com \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.