[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <91a64059-f301-4812-56ea-38755ccae5d7@collabora.com>
Date: Wed, 24 Nov 2021 12:56:09 -0300
From: André Almeida <andrealmeid@...labora.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Michal Simek <monstr@...str.eu>,
Michael Ellerman <mpe@...erman.id.au>,
Yoshinori Sato <ysato@...rs.sourceforge.jp>,
Rich Felker <dalias@...c.org>,
David Miller <davem@...emloft.net>,
Chris Zankel <chris@...kel.net>,
Max Filippov <jcmvbkbc@...il.com>,
alpha <linux-alpha@...r.kernel.org>, linux-ia64@...r.kernel.org,
linux-m68k <linux-m68k@...ts.linux-m68k.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Linux-sh list <linux-sh@...r.kernel.org>,
sparclinux <sparclinux@...r.kernel.org>,
"open list:TENSILICA XTENSA PORT (xtensa)"
<linux-xtensa@...ux-xtensa.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Boqun Feng <boqun.feng@...il.com>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
lkft-triage@...ts.linaro.org, Waiman Long <longman@...hat.com>,
Minchan Kim <minchan@...nel.org>,
Ingo Molnar <mingo@...hat.com>,
Naresh Kamboju <naresh.kamboju@...aro.org>,
Peter Zijlstra <peterz@...radead.org>,
Rob Landley <rob@...dley.net>,
Sergey Senozhatsky <senozhatsky@...omium.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Mike Galbraith <umgwanakikbuti@...il.com>,
Will Deacon <will@...nel.org>
Subject: Re: [PATCH 1/1] futex: Wireup futex_waitv syscall
Às 11:29 de 24/11/21, Arnd Bergmann escreveu:
> On Wed, Nov 24, 2021 at 2:21 PM André Almeida <andrealmeid@...labora.com> wrote:
>>
>> Wireup futex_waitv syscall for all remaining archs.
>>
>> Signed-off-by: André Almeida <andrealmeid@...labora.com>
>
> Reviewed-by: Arnd Bergmann <arnd@...db.de>
>
> I double-checked that futex_waitv() doesn't need any architecture specific
> hacks, and that the list above is complete.
Thanks!
>
> Should I take this through the asm-generic tree, or would you send it
> through the
> tip tree?
>
I think that adding it to asm-generic tree make sense to me.
Powered by blists - more mailing lists