From: Tejun Heo <tj@kernel.org>
To: Cheng-Yang Chou <yphbchou0911@gmail.com>
Cc: Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
David Vernet <void@manifault.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chia-Ping Tsai <chia7712@gmail.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched_ext: Fix inconsistent NUMA node lookup in scx_select_cpu_dfl()
Date: Sat, 21 Mar 2026 14:26:57 -1000 [thread overview]
Message-ID: <f3c39f973a13e73bb93bcdbb26c2f8e0@kernel.org> (raw)
In-Reply-To: <20260321193841.905994-1-yphbchou0911@gmail.com>
Hello,
The commit message on sched_ext/for-7.0-fixes has been amended to match
v2.
Thanks.
--
tejun
prev parent reply other threads:[~2026-03-22 0:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260321105503.869337-1-yphbchou0911@gmail.com>
2026-03-21 18:42 ` [PATCH] sched_ext: Fix inconsistent NUMA node lookup in scx_select_cpu_dfl() Tejun Heo
2026-03-21 19:39 ` Cheng-Yang Chou
[not found] ` <20260321193841.905994-1-yphbchou0911@gmail.com>
2026-03-22 0:26 ` Tejun Heo [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=f3c39f973a13e73bb93bcdbb26c2f8e0@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=chia7712@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.com \
--cc=yphbchou0911@gmail.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