From: kernel test robot <lkp@intel.com>
To: "André Almeida" <andrealmeid@collabora.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>
Subject: ../include/futex2test.h:18:47: warning: 'struct futex_waitv' declared inside parameter list will not be visible outside of this definition or declaration
Date: Tue, 19 Jul 2022 09:49:34 +0800 [thread overview]
Message-ID: <202207190947.pa3kz27F-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ca85855bdcae8f84f1512e88b4c75009ea17ea2f
commit: 5e59c1d1c78c9cdd8834f3242db4a76f617fa4ad selftests: futex: Add sys_futex_waitv() test
date: 10 months ago
reproduce: make O=/tmp/kselftest -C tools/testing/selftests
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from futex_waitv.c:19:
>> ../include/futex2test.h:18:47: warning: 'struct futex_waitv' declared inside parameter list will not be visible outside of this definition or declaration
18 | static inline int futex_waitv(volatile struct futex_waitv *waiters, unsigned long nr_waiters,
| ^~~~~~~~~~~
../include/futex2test.h: In function 'futex_waitv':
../include/futex2test.h:21:24: error: '__NR_futex_waitv' undeclared (first use in this function); did you mean 'futex_waitv'?
21 | return syscall(__NR_futex_waitv, waiters, nr_waiters, flags, timo, clockid);
| ^~~~~~~~~~~~~~~~
| futex_waitv
../include/futex2test.h:21:24: note: each undeclared identifier is reported only once for each function it appears in
futex_waitv.c: At top level:
futex_waitv.c:25:27: error: array type has incomplete element type 'struct futex_waitv'
25 | static struct futex_waitv waitv[NR_FUTEXES];
| ^~~~~
futex_waitv.c: In function 'main':
futex_waitv.c:91:34: error: 'FUTEX_32' undeclared (first use in this function); did you mean 'FUTEX_OP'?
91 | waitv[i].flags = FUTEX_32 | FUTEX_PRIVATE_FLAG;
| ^~~~~~~~
| FUTEX_OP
In file included from futex_waitv.c:19:
../include/futex2test.h: In function 'futex_waitv':
>> ../include/futex2test.h:22:1: warning: control reaches end of non-void function [-Wreturn-type]
22 | }
| ^
At top level:
>> futex_waitv.c:25:27: warning: 'waitv' defined but not used [-Wunused-variable]
25 | static struct futex_waitv waitv[NR_FUTEXES];
| ^~~~~
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-19 1:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202207190947.pa3kz27F-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrealmeid@collabora.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®