From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
x86@kernel.org
Subject: Re: [tip: locking/core] locking/futex/selftests: Remove duplicate ABI defines
Date: Fri, 6 Oct 2023 12:57:45 +0200 [thread overview]
Message-ID: <ZR/oKYY7R52wKYC5@gmail.com> (raw)
In-Reply-To: <20231006104325.GC36277@noisy.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> 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.
Hm, I did this after applying the patch, and it does work,
but maybe I missed that those definitions were picked up
from system headers...
So how about we make sure current kernel headers are applied
correctly in a 'standalone' build? There's no reason they
shouldn't be.
Thanks,
Ingo
next prev parent reply other threads:[~2023-10-06 10:57 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
2023-10-06 10:57 ` Ingo Molnar [this message]
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=ZR/oKYY7R52wKYC5@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.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