From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org
Subject: Re: Stable backport request
Date: Sun, 24 Oct 2021 13:49:00 +0200 [thread overview]
Message-ID: <YXVILOXgE9u/UOpM@kroah.com> (raw)
In-Reply-To: <87zgqzbcx6.fsf@mpe.ellerman.id.au>
On Sun, Oct 24, 2021 at 09:21:09AM +1100, Michael Ellerman wrote:
> Hi Greg,
>
> Please backport the following commit to v5.4 and v5.10:
>
> 73287caa9210ded6066833195f4335f7f688a46b
> ("powerpc64/idle: Fix SP offsets when saving GPRs")
>
>
> And please backport the following commits to v5.4, v5.10 and v5.14:
>
> 9b4416c5095c20e110c82ae602c254099b83b72f
> ("KVM: PPC: Book3S HV: Fix stack handling in idle_kvm_start_guest()")
>
> cdeb5d7d890e14f3b70e8087e745c4a6a7d9f337
> ("KVM: PPC: Book3S HV: Make idle_kvm_start_guest() return 0 if it went to guest")
>
> 496c5fe25c377ddb7815c4ce8ecfb676f051e9b6
> ("powerpc/idle: Don't corrupt back chain when going idle")
All now queued up, thanks!
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: stable@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Stable backport request
Date: Sun, 24 Oct 2021 13:49:00 +0200 [thread overview]
Message-ID: <YXVILOXgE9u/UOpM@kroah.com> (raw)
In-Reply-To: <87zgqzbcx6.fsf@mpe.ellerman.id.au>
On Sun, Oct 24, 2021 at 09:21:09AM +1100, Michael Ellerman wrote:
> Hi Greg,
>
> Please backport the following commit to v5.4 and v5.10:
>
> 73287caa9210ded6066833195f4335f7f688a46b
> ("powerpc64/idle: Fix SP offsets when saving GPRs")
>
>
> And please backport the following commits to v5.4, v5.10 and v5.14:
>
> 9b4416c5095c20e110c82ae602c254099b83b72f
> ("KVM: PPC: Book3S HV: Fix stack handling in idle_kvm_start_guest()")
>
> cdeb5d7d890e14f3b70e8087e745c4a6a7d9f337
> ("KVM: PPC: Book3S HV: Make idle_kvm_start_guest() return 0 if it went to guest")
>
> 496c5fe25c377ddb7815c4ce8ecfb676f051e9b6
> ("powerpc/idle: Don't corrupt back chain when going idle")
All now queued up, thanks!
greg k-h
next prev parent reply other threads:[~2021-10-24 22:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 22:21 Stable backport request Michael Ellerman
2021-10-23 22:21 ` Michael Ellerman
2021-10-24 11:49 ` Greg KH [this message]
2021-10-24 11:49 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2024-03-19 7:21 stable " Ard Biesheuvel
2024-03-24 21:23 ` Salvatore Bonaccorso
2022-12-21 14:50 Stable " Mimi Zohar
2022-12-21 18:22 ` Greg KH
2022-12-21 18:52 ` Mimi Zohar
2023-01-04 12:29 ` Greg KH
2013-01-24 9:58 stable " Daniel Vetter
2013-01-24 18:16 ` Greg KH
2013-01-24 18:59 ` Abdallah Chatila
2013-01-24 19:52 ` Greg KH
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=YXVILOXgE9u/UOpM@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=stable@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.