From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
"H . Peter Anvin" <hpa@zytor.com>, Paul Turner <pjt@google.com>,
linux-api@vger.kernel.org, Christian Brauner <brauner@kernel.org>,
Florian Weimer <fw@deneb.enyo.de>,
David.Laight@aculab.com, carlos@redhat.com,
Peter Oskolkov <posk@posk.io>,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Chris Kennelly <ckennelly@google.com>,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH tip] selftests/rseq: Revert "selftests/rseq: Add mm_numa_cid to test script"
Date: Wed, 11 Jan 2023 09:14:37 -0500 [thread overview]
Message-ID: <265a3900-45df-1b9a-b8de-85ef6d25141d@efficios.com> (raw)
In-Reply-To: <Y77D0+e2tdl8c1k1@hirez.programming.kicks-ass.net>
On 2023-01-11 09:12, Peter Zijlstra wrote:
> On Wed, Jan 04, 2023 at 11:35:42AM -0500, Mathieu Desnoyers wrote:
>> The mm_numa_cid related rseq patches from the series were not picked up
>> into the tip tree, so enabling the mm_numa_cid test needs to be
>> reverted.
>>
>> This reverts commit b344b8f2d88dbf095caf97ac57fd3645843fa70f.
>
> Oh my bad, I got confused between the regular numa_id (which I did do
> merge, right?) and the fancy numa_cid, which I indeed didn't merge yet.
Yes, that's indeed what happened.
> I meant to give that a wee bit more thought, but that sadly hasn't
> happened yet :/
>
> Applied, thanks!
No worries, let me know when you have time to discuss the fancy numa_cid
some more.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
prev parent reply other threads:[~2023-01-11 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 16:35 Mathieu Desnoyers
2023-01-11 14:12 ` Peter Zijlstra
2023-01-11 14:14 ` Mathieu Desnoyers [this message]
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=265a3900-45df-1b9a-b8de-85ef6d25141d@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=David.Laight@aculab.com \
--cc=alexander@mihalicyn.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=carlos@redhat.com \
--cc=ckennelly@google.com \
--cc=fw@deneb.enyo.de \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=posk@posk.io \
--cc=tglx@linutronix.de \
/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®