From: Arnd Bergmann <arnd@arndb.de>
To: Will Deacon <will.deacon@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
peter.maydell@linaro.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] asm-generic: unistd.h: Wire up sys_rseq
Date: Tue, 10 Jul 2018 23:32:09 +0200 [thread overview]
Message-ID: <CAK8P3a2oz0o+gi4W7OhU-2_55Kfk35MuHzhv+CgGAEWtWKF=0Q@mail.gmail.com> (raw)
In-Reply-To: <20180710175337.GD10177@arm.com>
On Tue, Jul 10, 2018 at 7:53 PM, Will Deacon <will.deacon@arm.com> wrote:
> Hi Arnd,
>
> On Mon, Jul 09, 2018 at 03:19:44PM +0100, Will Deacon wrote:
>> The new rseq call arrived in 4.18-rc1, so provide it in the asm-generic
>> unistd.h for architectures such as arm64.
>>
>> Cc: Arnd Bergmann <arnd@arndb.de>
>> Signed-off-by: Will Deacon <will.deacon@arm.com>
>> ---
>> include/uapi/asm-generic/unistd.h | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> Please can you Ack this, so I can take it the arm64 tree?
I just checked again that this syscall is compatible with
compat mode on all architectures that need it, so the
addition is safe.
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2018-07-10 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 14:19 [PATCH v2 0/3] Support rseq on arm64 Will Deacon
2018-07-09 14:19 ` [PATCH v2 1/3] arm64: rseq: Implement backend rseq calls and select HAVE_RSEQ Will Deacon
2018-07-09 14:19 ` [PATCH v2 2/3] asm-generic: unistd.h: Wire up sys_rseq Will Deacon
2018-07-10 17:53 ` Will Deacon
2018-07-10 21:32 ` Arnd Bergmann [this message]
2018-07-09 14:19 ` [PATCH v2 3/3] rseq/selftests: Add support for arm64 Will Deacon
2018-07-09 16:06 ` [PATCH v2 0/3] Support rseq on arm64 Mathieu Desnoyers
2018-07-09 16:53 ` Will Deacon
2018-07-09 17:17 ` Mathieu Desnoyers
2018-07-10 14:49 ` Will Deacon
2018-07-10 14:51 ` Mathieu Desnoyers
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='CAK8P3a2oz0o+gi4W7OhU-2_55Kfk35MuHzhv+CgGAEWtWKF=0Q@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.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).