From: Tejun Heo <tj@kernel.org>
To: Zqiang <qiang.zhang@linux.dev>
Cc: void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
qiang.zhang1211@gmail.com
Subject: Re: [PATCH] sched_ext: Use kvfree_rcu() to release per-cpu ksyncs object
Date: Mon, 17 Nov 2025 05:18:02 -1000 [thread overview]
Message-ID: <c679e72987c5414ceb1ca37cbdbcebd6@kernel.org> (raw)
In-Reply-To: <20251117125311.107687-2-qiang.zhang@linux.dev>
Applied to sched_ext/for-6.19.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-11-17 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 12:53 [PATCH] sched_ext: Use IRQ_WORK_INIT_HARD() to initialize rq->scx.kick_cpus_irq_work Zqiang
2025-11-17 12:53 ` [PATCH] sched_ext: Use kvfree_rcu() to release per-cpu ksyncs object Zqiang
2025-11-17 15:18 ` Tejun Heo [this message]
2025-11-17 15:15 ` [PATCH] sched_ext: Use IRQ_WORK_INIT_HARD() to initialize rq->scx.kick_cpus_irq_work Tejun Heo
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=c679e72987c5414ceb1ca37cbdbcebd6@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=qiang.zhang@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox