From: Thomas Gleixner <tglx@linutronix.de>
To: "kernel test robot" <lkp@intel.com>,
"André Almeida" <andrealmeid@igalia.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Waiman Long" <longman@redhat.com>,
"Ryan Houdek" <Sonicadvance1@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-api@vger.kernel.org,
kernel-dev@igalia.com, "André Almeida" <andrealmeid@igalia.com>
Subject: Re: [PATCH v6 6/9] futex: Wire up get_robust_list2 syscall
Date: Sun, 23 Nov 2025 19:47:51 +0100 [thread overview]
Message-ID: <87ms4cio14.ffs@tglx> (raw)
In-Reply-To: <202511221454.rsysOoSt-lkp@intel.com>
On Sat, Nov 22 2025 at 14:49, kernel test robot wrote:
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on c42ba5a87bdccbca11403b7ca8bad1a57b833732]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Andr-Almeida/futex-Use-explicit-sizes-for-compat_robust_list-structs/20251122-135406
> base: c42ba5a87bdccbca11403b7ca8bad1a57b833732
> patch link: https://lore.kernel.org/r/20251122-tonyk-robust_futex-v6-6-05fea005a0fd%40igalia.com
> patch subject: [PATCH v6 6/9] futex: Wire up get_robust_list2 syscall
> config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20251122/202511221454.rsysOoSt-lkp@intel.com/config)
> compiler: arc-linux-gcc (GCC) 15.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251122/202511221454.rsysOoSt-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202511221454.rsysOoSt-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>>> <stdin>:1627:2: warning: #warning syscall get_robust_list2 not implemented [-Wcpp]
> --
>>> <stdin>:1627:2: warning: #warning syscall get_robust_list2 not implemented [-Wcpp]
Lacks a COND_SYSCALL()
next prev parent reply other threads:[~2025-11-23 18:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-22 5:50 [PATCH v6 0/9] futex: Create {set,get}_robust_list2() syscalls André Almeida
2025-11-22 5:50 ` [PATCH v6 1/9] futex: Use explicit sizes for compat_robust_list structs André Almeida
2025-11-22 5:50 ` [PATCH v6 2/9] futex: Make exit_robust_list32() unconditionally available for 64-bit kernels André Almeida
2025-11-22 5:50 ` [PATCH v6 3/9] futex: Create set_robust_list2() syscall André Almeida
2025-11-22 5:50 ` [PATCH v6 4/9] futex: Create get_robust_list2() syscall André Almeida
2025-11-23 7:16 ` kernel test robot
2025-11-23 10:02 ` kernel test robot
2025-11-22 5:50 ` [PATCH v6 5/9] futex: Wire up set_robust_list2 syscall André Almeida
2025-11-22 5:50 ` [PATCH v6 6/9] futex: Wire up get_robust_list2 syscall André Almeida
2025-11-22 6:49 ` kernel test robot
2025-11-23 18:47 ` Thomas Gleixner [this message]
2025-11-23 19:19 ` Arnd Bergmann
2025-11-23 20:02 ` Thomas Gleixner
2025-11-22 7:32 ` kernel test robot
2025-11-22 7:44 ` kernel test robot
2025-11-22 5:50 ` [PATCH v6 7/9] selftests/futex: Expand for set_robust_list2() André Almeida
2025-11-22 5:50 ` [PATCH v6 8/9] selftests/futex: Expand for get_robust_list2() André Almeida
2025-11-22 5:50 ` [PATCH v6 9/9] futex: Use new robust list API internally André Almeida
2025-11-22 14:25 ` [PATCH v6 0/9] futex: Create {set,get}_robust_list2() syscalls André Almeida
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=87ms4cio14.ffs@tglx \
--to=tglx@linutronix.de \
--cc=Sonicadvance1@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=arnd@arndb.de \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=kernel-dev@igalia.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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 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.