From: Greg KH <greg@kroah.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: fedora.dm0@gmail.com, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH for 5.10] powerpc/32: Preserve cr1 in exception prolog stack check to fix build error
Date: Mon, 15 Feb 2021 15:30:55 +0100 [thread overview]
Message-ID: <YCqFn/4YuT+445xW@kroah.com> (raw)
In-Reply-To: <f6d16f3321f1dc89b77ada1c7d961fae4089766e.1613120077.git.christophe.leroy@csgroup.eu>
On Fri, Feb 12, 2021 at 08:57:14AM +0000, Christophe Leroy wrote:
> This is backport of 3642eb21256a ("powerpc/32: Preserve cr1 in
> exception prolog stack check to fix build error") for kernel 5.10
>
> It fixes the build failure on v5.10 reported by kernel test robot
> and by David Michael.
>
> This fix is not in Linux tree yet, it is in next branch in powerpc tree.
Then there's nothing I can do about it until that happens :(
next prev parent reply other threads:[~2021-02-15 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 8:57 [PATCH for 5.10] powerpc/32: Preserve cr1 in exception prolog stack check to fix build error Christophe Leroy
2021-02-15 14:30 ` Greg KH [this message]
2021-02-23 14:39 ` Christophe Leroy
2021-03-01 13:14 ` 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=YCqFn/4YuT+445xW@kroah.com \
--to=greg@kroah.com \
--cc=christophe.leroy@csgroup.eu \
--cc=fedora.dm0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox