public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	x86@kernel.org
Subject: Re: [tip: locking/core] locking/futex/selftests: Remove duplicate ABI defines
Date: Fri, 6 Oct 2023 13:17:01 +0200	[thread overview]
Message-ID: <20231006111701.GF36277@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <1b9a4e52-cfa3-4f56-b259-41c94abed362@collabora.com>

On Fri, Oct 06, 2023 at 04:05:31PM +0500, Muhammad Usama Anjum wrote:

> These days a error should appear if the kernel headers aren't found at
> build time of kselftests. After building headers, kselftests should be build.
> 
> ➜  functional (06bc8fe4bfc4b) ✗ pwd
> /linux_mainline/tools/testing/selftests/futex/functional
> ➜  functional (06bc8fe4bfc4b) ✗ make
> 
> -e error: missing kernel header files.

Obviously I don't see that. And I would consider this a regression.
Since it means I can't build tests anymore.

  parent reply	other threads:[~2023-10-06 11:17 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
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 [this message]
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=20231006111701.GF36277@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