From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>
Cc: sched-ext@lists.linux.dev, Emil Tsalapatis <emil@etsalapatis.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHSET sched_ext/for-7.3] sched_ext: NMI-safe exit handling
Date: Mon, 27 Jul 2026 11:24:48 -1000 [thread overview]
Message-ID: <952f200652a9a7e89ac2eb0364ed74f6@kernel.org> (raw)
In-Reply-To: <20260725005019.1297049-1-tj@kernel.org>
On Fri, Jul 24, 2026 at 02:50:14PM -1000, Tejun Heo wrote:
> 0001-sched_ext-Make-exit-claiming-lock-free.patch
> 0002-sched_ext-Format-bstr-exit-messages-after-claiming-t.patch
> 0003-sched_ext-Report-NMI-kicks-with-scx_error.patch
> 0004-sched_ext-Abort-directly-from-the-hardlockup-handler.patch
> 0005-sched_ext-Report-scx_link_sched-failures-inline.patch
Applied 1-5 (1 in its v2 form) to sched_ext/for-7.3 with Andrea's
Reviewed-by added.
Thanks.
--
tejun
prev parent reply other threads:[~2026-07-27 21:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-25 0:50 [PATCHSET sched_ext/for-7.3] sched_ext: NMI-safe exit handling Tejun Heo
2026-07-25 0:50 ` [PATCH 1/5] sched_ext: Make exit claiming lock-free Tejun Heo
2026-07-27 19:35 ` Andrea Righi
2026-07-27 20:36 ` [PATCH v2 " Tejun Heo
2026-07-25 0:50 ` [PATCH 2/5] sched_ext: Format bstr exit messages after claiming the exit Tejun Heo
2026-07-25 0:50 ` [PATCH 3/5] sched_ext: Report NMI kicks with scx_error() Tejun Heo
2026-07-25 0:50 ` [PATCH 4/5] sched_ext: Abort directly from the hardlockup handler Tejun Heo
2026-07-25 0:50 ` [PATCH 5/5] sched_ext: Report scx_link_sched() failures inline Tejun Heo
2026-07-27 21:17 ` [PATCHSET sched_ext/for-7.3] sched_ext: NMI-safe exit handling Andrea Righi
2026-07-27 21:24 ` 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=952f200652a9a7e89ac2eb0364ed74f6@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=void@manifault.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.