From: "André Almeida" <andrealmeid@igalia.com>
To: Borislav Petkov <bp@alien8.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Waiman Long <llong@redhat.com>,
Darren Hart <dvhart@infradead.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Schneider <vschneid@redhat.com>,
kernel-dev@igalia.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/futex: Fix futex_numa_mpol's memory out of range subtest
Date: Mon, 1 Sep 2025 09:49:14 -0300 [thread overview]
Message-ID: <64deb0ae-5641-4ceb-889e-0ef1087175fb@igalia.com> (raw)
In-Reply-To: <20250829100705.GBaLF7ycOvksu9H6KN@fat_crate.local>
Em 29/08/2025 07:07, Borislav Petkov escreveu:
> On Fri, Aug 29, 2025 at 08:16:24AM +0200, Sebastian Andrzej Siewior wrote:
>>> No objections merging Waiman fix first, but we are still in -rc3, so maybe
>>> there's time for the rework in this cycle?
>
> ... and you can rework all you want. When your solution is ready and everyone
> agrees, there's nothing wrong with queueing it ontop or delaying it for the
> next merge window.
>
>> On the regression list, we this one fallout in the testsuite. I would
>> like to get an easy fix for -rc4 and be done with it for this cycle.
>
> There's absolutely no place for hurrying things, especially for self tests. So
> take your time pls.
>
Sure, I don't want to hurry things, I'm just trying to understand better
the rationale of having this for the next cycle, and if I would have to
wait or not till the next kernel release to send the patch :)
next prev parent reply other threads:[~2025-09-01 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 15:44 André Almeida
2025-08-27 17:58 ` Waiman Long
2025-08-28 6:32 ` Sebastian Andrzej Siewior
2025-08-28 18:06 ` André Almeida
2025-08-28 18:20 ` Sebastian Andrzej Siewior
2025-08-28 18:47 ` Waiman Long
2025-08-29 2:22 ` André Almeida
2025-08-29 6:16 ` Sebastian Andrzej Siewior
2025-08-29 10:07 ` Borislav Petkov
2025-09-01 12:49 ` André Almeida [this message]
2025-09-01 13:57 ` Borislav Petkov
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=64deb0ae-5641-4ceb-889e-0ef1087175fb@igalia.com \
--to=andrealmeid@igalia.com \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=juri.lelli@redhat.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®