From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org
Subject: Re: [tip: locking/core] locking/futex/selftests: Remove duplicate ABI defines
Date: Fri, 6 Oct 2023 12:43:25 +0200 [thread overview]
Message-ID: <20231006104325.GC36277@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <169658834039.3135.4395839213523782496.tip-bot2@tip-bot2>
On Fri, Oct 06, 2023 at 10:32:20AM -0000, tip-bot2 for Muhammad Usama Anjum wrote:
> The following commit has been merged into the locking/core branch of tip:
>
> Commit-ID: d351a9e56cc90a9ff694550e4b3bcaf51a391525
> Gitweb: https://git.kernel.org/tip/d351a9e56cc90a9ff694550e4b3bcaf51a391525
> Author: Muhammad Usama Anjum <usama.anjum@collabora.com>
> AuthorDate: Fri, 06 Oct 2023 14:55:37 +05:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Fri, 06 Oct 2023 12:29:45 +02:00
>
> locking/futex/selftests: Remove duplicate ABI defines
>
> Kselftests are kernel tests that are built with kernel headers
> from the same source version. The kernel headers, which includes
> current ABI definitions, are already being included correctly
> in the futex selftest Makefile with the help of KHDR_INCLUDE,
> no need to define them again.
>
> Remove duplicate ABI definitions, which is effectively dead code.
>
> No functional changes intended.
so.. as it happens I recently built these things as stand-alone, and
then you ver much end up using the system headers.
Also see 20230922205449.808782861@infradead.org where I add more of
this.
Specifically, if one does:
cd tools/testing/selftests/futex/functional; make
You don't get kernel headers and stuff does not build.
So no, I don't think this is superfluous.
>
> Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> Link: https://lore.kernel.org/r/20231006095539.1601385-1-usama.anjum@collabora.com
> ---
> tools/testing/selftests/futex/include/futextest.h | 22 +--------------
> 1 file changed, 22 deletions(-)
>
> diff --git a/tools/testing/selftests/futex/include/futextest.h b/tools/testing/selftests/futex/include/futextest.h
> index ddbcfc9..59f66af 100644
> --- a/tools/testing/selftests/futex/include/futextest.h
> +++ b/tools/testing/selftests/futex/include/futextest.h
> @@ -25,28 +25,6 @@
> typedef volatile u_int32_t futex_t;
> #define FUTEX_INITIALIZER 0
>
> -/* Define the newer op codes if the system header file is not up to date. */
> -#ifndef FUTEX_WAIT_BITSET
> -#define FUTEX_WAIT_BITSET 9
> -#endif
> -#ifndef FUTEX_WAKE_BITSET
> -#define FUTEX_WAKE_BITSET 10
> -#endif
> -#ifndef FUTEX_WAIT_REQUEUE_PI
> -#define FUTEX_WAIT_REQUEUE_PI 11
> -#endif
> -#ifndef FUTEX_CMP_REQUEUE_PI
> -#define FUTEX_CMP_REQUEUE_PI 12
> -#endif
> -#ifndef FUTEX_WAIT_REQUEUE_PI_PRIVATE
> -#define FUTEX_WAIT_REQUEUE_PI_PRIVATE (FUTEX_WAIT_REQUEUE_PI | \
> - FUTEX_PRIVATE_FLAG)
> -#endif
> -#ifndef FUTEX_REQUEUE_PI_PRIVATE
> -#define FUTEX_CMP_REQUEUE_PI_PRIVATE (FUTEX_CMP_REQUEUE_PI | \
> - FUTEX_PRIVATE_FLAG)
> -#endif
> -
> /**
> * futex() - SYS_futex syscall wrapper
> * @uaddr: address of first futex
next prev parent reply other threads:[~2023-10-06 10:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 9:55 [PATCH v2] selftests: futex: remove duplicate unneeded defines Muhammad Usama Anjum
2023-10-06 10:32 ` [tip: locking/core] locking/futex/selftests: Remove duplicate ABI defines tip-bot2 for Muhammad Usama Anjum
2023-10-06 10:43 ` Peter Zijlstra [this message]
2023-10-06 10:57 ` Ingo Molnar
2023-10-06 11:04 ` Ingo Molnar
2023-10-06 11:05 ` Muhammad Usama Anjum
2023-10-06 11:12 ` Peter Zijlstra
2023-10-06 11:17 ` Peter Zijlstra
2023-10-06 11:13 ` Peter Zijlstra
2023-10-16 19:21 ` [PATCH v2] selftests: futex: remove duplicate unneeded defines Shuah Khan
2023-10-16 21:43 ` Peter Zijlstra
2023-10-18 19:11 ` Shuah Khan
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=20231006104325.GC36277@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=usama.anjum@collabora.com \
--cc=x86@kernel.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