From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <pmac@au1.ibm.com>
Subject: Re: [RFC PATCH 1/2] powerpc/powernv: Remove separate entry for OPAL real mode calls
Date: Tue, 07 Feb 2017 14:55:37 +1100 [thread overview]
Message-ID: <1486439737.4850.111.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170207025105.GG21840@gate.crashing.org>
On Mon, 2017-02-06 at 20:51 -0600, Segher Boessenkool wrote:
> On Tue, Feb 07, 2017 at 01:17:59PM +1100, Benjamin Herrenschmidt
> wrote:
> > @@ -123,7 +149,6 @@ opal_tracepoint_entry:
> > ld r9,STK_REG(R30)(r1)
> > ld r10,STK_REG(R31)(r1)
> > LOAD_REG_ADDR(r11,opal_tracepoint_return)
> > - mfcr r12
> > std r11,16(r1)
> > stw r12,8(r1)
> > li r11,0
>
> I think you accidentally deleted this line?
Correct.
Cheers,
Ben.
next prev parent reply other threads:[~2017-02-07 3:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 2:17 [RFC PATCH 1/2] powerpc/powernv: Remove separate entry for OPAL real mode calls Benjamin Herrenschmidt
2017-02-07 2:51 ` Segher Boessenkool
2017-02-07 3:55 ` Benjamin Herrenschmidt [this message]
2017-02-07 5:03 ` [PATCH v2] " Paul Mackerras
2017-02-08 0:31 ` [v2] " 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=1486439737.4850.111.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=pmac@au1.ibm.com \
--cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).