From: "André Almeida" <andrealmeid@collabora.com>
To: Arnd Bergmann <arnd@arndb.de>, Rob Landley <rob@landley.net>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
lkft-triage@lists.linaro.org
Subject: Re: spinlock.c:306:9: error: implicit declaration of function '__raw_write_lock_nested'
Date: Wed, 24 Nov 2021 10:15:52 -0300 [thread overview]
Message-ID: <4dd8a108-013f-8d68-b5d5-138d3cf3bff0@collabora.com> (raw)
In-Reply-To: <CAK8P3a3pQW59NVF=5P+ZiBjNJmnWh+iTZUHvqHBrXkHA6pMd4g@mail.gmail.com>
Hi Arnd,
Às 04:49 de 24/11/21, Arnd Bergmann escreveu:
> On Wed, Nov 24, 2021 at 8:31 AM Rob Landley <rob@landley.net> wrote:
>> On 11/23/21 5:38 AM, Naresh Kamboju wrote:
>> @@ -451,3 +451,4 @@
>> 446 common landlock_restrict_self sys_landlock_restrict_self
>> # 447 reserved for memfd_secret
>> 448 common process_mrelease sys_process_mrelease
>> +449 common futex_waitv sys_futex_waitv
>
> I don't know what's going on with this one, I don't actually see
> a reason why it isn't already wired up on all architectures. If we add
> this, it should probably be done for all architectures at once as a
> bugfix, but it's possible that this is intentionally only used on
> x86 and arm.
>
> André, can you comment on this?
>
> Arnd
>
I've added entries for the archs that I've actually tested, but there
should not be any arch-specific problems in futex_waitv. I'll submit a
patch to wire it up for the remaining architectures.
next prev parent reply other threads:[~2021-11-24 14:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 11:38 spinlock.c:306:9: error: implicit declaration of function '__raw_write_lock_nested' Naresh Kamboju
2021-11-23 13:19 ` Arnd Bergmann
2021-11-23 14:48 ` Geert Uytterhoeven
2021-11-23 14:50 ` Sebastian Andrzej Siewior
2021-11-23 16:07 ` [PATCH] locking: Fixup write_lock_nested() implementation Sebastian Andrzej Siewior
2021-11-23 17:01 ` [PATCH v2] " Sebastian Andrzej Siewior
2021-11-23 22:52 ` Stephen Rothwell
2021-11-24 10:01 ` spinlock.c:306:9: error: implicit declaration of function '__raw_write_lock_nested' Rob Landley
2021-11-24 10:43 ` Arnd Bergmann
2021-11-24 7:31 ` Rob Landley
2021-11-24 7:49 ` Arnd Bergmann
2021-11-24 13:15 ` André Almeida [this message]
2021-11-24 14:21 ` Arnd Bergmann
2021-11-24 13:21 ` [PATCH 1/1] futex: Wireup futex_waitv syscall André Almeida
2021-11-24 13:21 ` André Almeida
2021-11-24 13:21 ` André Almeida
2021-11-24 13:21 ` André Almeida
2021-11-24 13:49 ` Geert Uytterhoeven
2021-11-24 13:49 ` Geert Uytterhoeven
2021-11-24 13:49 ` Geert Uytterhoeven
2021-11-24 13:49 ` Geert Uytterhoeven
2021-11-24 14:29 ` Arnd Bergmann
2021-11-24 14:29 ` Arnd Bergmann
2021-11-24 14:29 ` Arnd Bergmann
2021-11-24 14:29 ` Arnd Bergmann
2021-11-24 15:56 ` André Almeida
2021-11-24 15:56 ` André Almeida
2021-11-24 15:56 ` André Almeida
2021-11-24 15:56 ` André Almeida
2021-11-24 23:18 ` Thomas Gleixner
2021-11-24 23:18 ` Thomas Gleixner
2021-11-24 23:18 ` Thomas Gleixner
2021-11-24 23:18 ` Thomas Gleixner
2021-11-24 17:23 ` Max Filippov
2021-11-24 17:23 ` Max Filippov
2021-11-24 17:23 ` Max Filippov
2021-11-24 17:23 ` Max Filippov
2021-11-24 23:07 ` Michael Ellerman
2021-11-24 23:07 ` Michael Ellerman
2021-11-24 23:07 ` Michael Ellerman
2021-11-24 23:07 ` Michael Ellerman
2021-11-24 23:38 ` spinlock.c:306:9: error: implicit declaration of function '__raw_write_lock_nested' Rob Landley
2021-11-25 7:25 ` Arnd Bergmann
2021-11-25 12:10 ` Rob Landley
2021-11-26 23:51 ` Stafford Horne
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=4dd8a108-013f-8d68-b5d5-138d3cf3bff0@collabora.com \
--to=andrealmeid@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=dalias@libc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=longman@redhat.com \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=rob@landley.net \
--cc=senozhatsky@chromium.org \
--cc=sfr@canb.auug.org.au \
--cc=umgwanakikbuti@gmail.com \
--cc=will@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.