From: Michael Ellerman <mpe@ellerman.id.au>
To: Nicholas Piggin <npiggin@gmail.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH] powerpc/64s: power4 nap fixup in C
Date: Mon, 29 Mar 2021 15:40:36 +1100 [thread overview]
Message-ID: <87y2e6fu7v.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20210312012044.3660743-1-npiggin@gmail.com>
Nicholas Piggin <npiggin@gmail.com> writes:
> There is no need for this to be in asm, use the new intrrupt entry wrapper.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> Hopefully this works on a real G5 now, but I couldn't reproduce the
> problem with QEMU.
It still prevents my G5 from booting.
Next time someone is in the office I'll ask them to check the display to
see if there's an oops.
cheers
next prev parent reply other threads:[~2021-03-29 4:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 1:20 [PATCH] powerpc/64s: power4 nap fixup in C Nicholas Piggin
2021-03-16 7:16 ` Christophe Leroy
2021-03-16 8:11 ` Nicholas Piggin
2021-03-29 4:40 ` Michael Ellerman [this message]
2021-03-29 8:33 ` Benjamin Herrenschmidt
2021-03-29 9:04 ` Christophe Leroy
[not found] ` <236a67a4-1609-5fec-3c68-41db02cd1a4c__18973.8760514714$1617008745$gmane$org@csgroup.eu>
2021-03-29 11:56 ` Andreas Schwab
[not found] ` <87czvikwb7.fsf__13924.9042653077$1617019017$gmane$org@igel.home>
2021-03-29 16:51 ` Andreas Schwab
[not found] ` <87y2e6fu7v.fsf__9754.75274478725$1616992871$gmane$org@mpe.ellerman.id.au>
2021-03-29 15:30 ` Andreas Schwab
[not found] ` <87v99aj7tr.fsf__47134.2879392736$1617031867$gmane$org@igel.home>
2021-03-29 16:23 ` Andreas Schwab
2021-04-01 7:36 ` Nicholas Piggin
2021-04-05 12:56 ` Nicholas Piggin
2021-04-05 16:40 ` Andreas Schwab
2021-04-06 2:45 ` Nicholas Piggin
2021-04-10 14:28 ` Michael Ellerman
2021-04-19 5:16 ` 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=87y2e6fu7v.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.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).