From: Greg KH <gregkh@linuxfoundation•org>
To: Michael Ellerman <mpe@ellerman•id.au>
Cc: linuxppc-dev@lists•ozlabs.org, npiggin@gmail•com, stable@vger•kernel.org
Subject: Re: [PATCH v4.19 0/2] Custom backports for powerpc SLB issues
Date: Fri, 29 Apr 2022 10:56:38 +0200 [thread overview]
Message-ID: <YmuoRmZHtJpx5pzT@kroah.com> (raw)
In-Reply-To: <20220428124150.375623-1-mpe@ellerman.id.au>
On Thu, Apr 28, 2022 at 10:41:48PM +1000, Michael Ellerman wrote:
> Hi Greg,
>
> Here are two custom backports to v4.19 for some powerpc issues we've discovered.
> Both were fixed upstream as part of a large non-backportable rewrite. Other stable
> kernel versions are not affected.
>
> cheers
>
> Michael Ellerman (1):
> powerpc/64s: Unmerge EX_LR and EX_DAR
>
> Nicholas Piggin (1):
> powerpc/64/interrupt: Temporarily save PPR on stack to fix register
> corruption due to SLB miss
>
> arch/powerpc/include/asm/exception-64s.h | 37 ++++++++++++++----------
> 1 file changed, 22 insertions(+), 15 deletions(-)
>
> --
> 2.35.1
>
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-04-29 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 12:41 [PATCH v4.19 0/2] Custom backports for powerpc SLB issues Michael Ellerman
2022-04-28 12:41 ` [PATCH v4.19 1/2] powerpc/64/interrupt: Temporarily save PPR on stack to fix register corruption due to SLB miss Michael Ellerman
2022-04-29 8:57 ` Patch "powerpc/64/interrupt: Temporarily save PPR on stack to fix register corruption due to SLB miss" has been added to the 4.19-stable tree gregkh
2022-04-28 12:41 ` [PATCH v4.19 2/2] powerpc/64s: Unmerge EX_LR and EX_DAR Michael Ellerman
2022-04-29 8:57 ` Patch "powerpc/64s: Unmerge EX_LR and EX_DAR" has been added to the 4.19-stable tree gregkh
2022-04-29 8:56 ` Greg KH [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=YmuoRmZHtJpx5pzT@kroah.com \
--to=gregkh@linuxfoundation$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=stable@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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