From: Finn Thain <fthain@linux-m68k.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
userm57@yahoo.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/32s: Fix napping restore in data storage interrupt (DSI)
Date: Thu, 5 Aug 2021 11:54:29 +1000 (AEST) [thread overview]
Message-ID: <cec92a8a-34a0-6c5c-20e1-7de7d768a596@linux-m68k.org> (raw)
In-Reply-To: <b04a90a9-9d62-2192-f896-ea99be911604@csgroup.eu>
On Wed, 4 Aug 2021, Christophe Leroy wrote:
>
> This patch is related to the bisect you did that pointed to 4c0104a83fc3
> ("powerpc/32: Dismantle EXC_XFER_STD/LITE/TEMPLATE")
>
> I think maybe the starting point should be to (manually) apply the patch
> on top of that commit in order to check that the bug to leaded to
> pointing that commit as 'first bad commit' is now gone.
>
Stan has now confirmed this. He applied this patch on top of 4c0104a83fc3,
and it did indeed resolve the bug that 'git bisect' isolated [1]. Thanks
Christophe.
[1]
https://lore.kernel.org/lkml/666e3ab4-372-27c2-4621-7cc3933756dd@linux-m68k.org/
next prev parent reply other threads:[~2021-08-05 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 15:14 [PATCH] powerpc/32s: Fix napping restore in data storage interrupt (DSI) Christophe Leroy
2021-08-04 4:04 ` Finn Thain
2021-08-04 6:07 ` Christophe Leroy
2021-08-04 6:21 ` Christophe Leroy
2021-08-04 11:36 ` Nicholas Piggin
2021-08-04 13:28 ` Christophe Leroy
2021-08-04 14:45 ` Nicholas Piggin
2021-08-05 1:54 ` Finn Thain [this message]
2021-08-13 11:57 ` Michael Ellerman
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=cec92a8a-34a0-6c5c-20e1-7de7d768a596@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=userm57@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).