From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 3/4] powerpc/64: system call remove non-volatile GPR save optimisation
Date: Tue, 27 Aug 2019 03:10:43 -0500 [thread overview]
Message-ID: <20190827081043.GU31406@gate.crashing.org> (raw)
In-Reply-To: <20190827033010.28090-5-npiggin@gmail.com>
On Tue, Aug 27, 2019 at 01:30:09PM +1000, Nicholas Piggin wrote:
> -435 nospu clone3 ppc_clone3
> +435 32 clone3 ppc_clone3 sys_clone3
> +435 64 clone3 sys_clone3
> +435 nospu clone3 sys_ni_syscall
s/no// on that last line. Rest looks good to me :-)
Segher
next prev parent reply other threads:[~2019-08-27 8:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 3:30 [PATCH 0/4] powerpc/64: syscalls in C Nicholas Piggin
2019-08-27 3:30 ` [PATCH 1/4] powerpc: convert to copy_thread_tls Nicholas Piggin
2019-08-27 6:07 ` Christophe Leroy
2019-08-27 10:13 ` Nicholas Piggin
2019-08-27 14:00 ` Christophe Leroy
2019-09-02 3:29 ` Michael Ellerman
2019-08-27 3:30 ` [PATCH 2/4] powerpc/64: remove support for kernel-mode syscalls Nicholas Piggin
2019-08-27 6:13 ` Christophe Leroy
2019-08-27 10:20 ` Nicholas Piggin
2019-08-27 10:41 ` Nicholas Piggin
2019-08-27 3:30 ` [PATCH 2/4] powerpc/64s: " Nicholas Piggin
2019-08-27 6:14 ` Christophe Leroy
2019-08-27 10:21 ` Nicholas Piggin
2019-08-27 3:30 ` [PATCH 3/4] powerpc/64: system call remove non-volatile GPR save optimisation Nicholas Piggin
2019-08-27 8:10 ` Segher Boessenkool [this message]
2019-08-27 3:30 ` [PATCH 4/4] powerpc/64: system call implement the bulk of the logic in C Nicholas Piggin
2019-08-27 6:46 ` Christophe Leroy
2019-08-27 10:30 ` Nicholas Piggin
2019-08-27 14:35 ` 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=20190827081043.GU31406@gate.crashing.org \
--to=segher@kernel.crashing.org \
--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).