From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, usama.anjum@collabora.com,
tglx@linutronix.de, shuah@kernel.org, peterz@infradead.org,
ndesaulniers@google.com, nathan@kernel.org, morbo@google.com,
mingo@redhat.com, justinstitt@google.com, edliaw@google.com,
dvhart@infradead.org, dave@stgolabs.net, colin.i.king@gmail.com,
andrealmeid@igalia.com, ywen.chen@foxmail.com
Subject: Re: + selftests-futex-fix-the-failed-futex_requeue-test-issue.patch added to mm-nonmm-unstable branch
Date: Tue, 27 Jan 2026 08:07:00 +0100 [thread overview]
Message-ID: <20260127070700.Kho5amle@linutronix.de> (raw)
In-Reply-To: <20260126195016.AE9B7C116C6@smtp.kernel.org>
On 2026-01-26 11:50:16 [-0800], Andrew Morton wrote:
>
> The patch titled
> Subject: selftests/futex: fix the failed futex_requeue test issue
> has been added to the -mm mm-nonmm-unstable branch. Its filename is
> selftests-futex-fix-the-failed-futex_requeue-test-issue.patch
>
> This patch will shortly appear at
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/selftests-futex-fix-the-failed-futex_requeue-test-issue.patch
>
> This patch will later appear in the mm-nonmm-unstable branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
>
> Before you just go and hit "reply", please:
> a) Consider who else should be cc'ed
> b) Prefer to cc a suitable mailing list as well
> c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
Please don't send it any further before someone acks it. It is on my
list for some time now…
Sebastian
next prev parent reply other threads:[~2026-01-27 7:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 19:50 + selftests-futex-fix-the-failed-futex_requeue-test-issue.patch added to mm-nonmm-unstable branch Andrew Morton
2026-01-27 7:07 ` Sebastian Andrzej Siewior [this message]
2026-01-27 18:33 ` Thomas Gleixner
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=20260127070700.Kho5amle@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=colin.i.king@gmail.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=edliaw@google.com \
--cc=justinstitt@google.com \
--cc=mingo@redhat.com \
--cc=mm-commits@vger.kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=usama.anjum@collabora.com \
--cc=ywen.chen@foxmail.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 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.