From: Peter Zijlstra <peterz@infradead.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: "Muhammad Usama Anjum" <usama.anjum@collabora.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Shuah Khan" <shuah@kernel.org>,
kernel@collabora.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2] selftests: futex: remove duplicate unneeded defines
Date: Mon, 16 Oct 2023 23:43:42 +0200 [thread overview]
Message-ID: <20231016214342.GC36211@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <7f6380ca-7f4e-4080-a047-6f7d427c3501@linuxfoundation.org>
On Mon, Oct 16, 2023 at 01:21:20PM -0600, Shuah Khan wrote:
> On 10/6/23 03:55, Muhammad Usama Anjum wrote:
> > Kselftests are kernel tests and must be build with kernel headers from
> > same source version. The kernel headers are already being included
> > correctly in futex selftest Makefile with the help of KHDR_INCLUDE. In
> > this patch, only the dead code is being removed. No functional change is
> > intended.
> >
> > Signed-off-by: Muhammad Usama Anjum <usama.anjum@collabora.com>
> > ---
>
> Applied to linux-kselftest next for Linux 6.7-rc1.
Please don't.
next prev parent reply other threads:[~2023-10-16 21:44 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
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 [this message]
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=20231016214342.GC36211@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrealmeid@igalia.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=usama.anjum@collabora.com \
/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