From: Leonardo Bras <leobras.c@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>,
Allison Randal <allison@lohutok.net>,
Thiago Jung Bauermann <bauerman@linux.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Daniel Axtens <dja@axtens.net>,
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Anshuman Khandual <khandual@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nadav Amit <namit@vmware.com>,
Nathan Lynch <nathanl@linux.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] powerpc/rtas: Implement reentrant rtas call
Date: Mon, 18 May 2020 20:40:34 -0300 [thread overview]
Message-ID: <2ccc819dba70152bc57cf375a8f792a28a3c433f.camel@gmail.com> (raw)
In-Reply-To: <1589614523.yfijifo1n6.astroid@bobo.none>
On Sat, 2020-05-16 at 17:36 +1000, Nicholas Piggin wrote:
> Good, I think this should work as you want now. Can you allocate it like
> lppacas? Put it under PSERIES (and in the paca) and check for !HV?
Sure, I will do that.
> Oh and while there, could you prefix the name with rtas_?
Sure, replacing reentrant_args with rtas_args_reentrant.
>
> Thanks,
> Nick
Thank you for the feedback!
Leonardo Bras
next prev parent reply other threads:[~2020-05-18 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 5:21 [PATCH v5 0/2] Implement reentrant rtas call Leonardo Bras
2020-05-16 5:21 ` [PATCH v5 1/2] powerpc/rtas: Move type/struct definitions from rtas.h into rtas-types.h Leonardo Bras
2020-05-16 5:21 ` [PATCH v5 2/2] powerpc/rtas: Implement reentrant rtas call Leonardo Bras
2020-05-16 7:36 ` Nicholas Piggin
2020-05-17 22:52 ` Nicholas Piggin
2020-05-18 23:40 ` Leonardo Bras [this message]
2020-05-16 12:15 ` kbuild test robot
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=2ccc819dba70152bc57cf375a8f792a28a3c433f.camel@gmail.com \
--to=leobras.c@gmail.com \
--cc=allison@lohutok.net \
--cc=bauerman@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=dja@axtens.net \
--cc=ego@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=namit@vmware.com \
--cc=nathanl@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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).