From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Paul Mackerras <paulus@ozlabs.org>, linuxppc-dev@ozlabs.org
Subject: Re: [v2] powerpc/powernv: Remove separate entry for OPAL real mode calls
Date: Wed, 8 Feb 2017 11:31:29 +1100 (AEDT) [thread overview]
Message-ID: <3vJ2FY3XKCz9s73@ozlabs.org> (raw)
In-Reply-To: <20170207050317.GA10303@fergus.ozlabs.ibm.com>
On Tue, 2017-02-07 at 05:03:17 UTC, Paul Mackerras wrote:
> From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>
> All entry points already read the MSR so they can easily do
> the right thing.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Applied to topic/ppc-kvm, thanks.
https://git.kernel.org/powerpc/c/ab9bad0ead9ab179ace09988a3f1cf
cheers
prev parent reply other threads:[~2017-02-08 0:31 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
2017-02-07 5:03 ` [PATCH v2] " Paul Mackerras
2017-02-08 0:31 ` Michael Ellerman [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=3vJ2FY3XKCz9s73@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@ozlabs.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).