From: Tejun Heo <tj@kernel.org>
To: Xin Zhao <jackzxcui1989@163.com>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: Support RT workqueue
Date: Fri, 17 Oct 2025 05:16:40 -1000 [thread overview]
Message-ID: <aPJd2PggjJwMUs4Q@slm.duckdns.org> (raw)
In-Reply-To: <aPJdrqSiuijOcaPE@slm.duckdns.org>
On Fri, Oct 17, 2025 at 05:15:58AM -1000, Tejun Heo wrote:
> There are a couple reasons why I don't think we don't want to go this way:
Sorry about the double negative. Drop one of them.
Thanks.
--
tejun
next prev parent reply other threads:[~2025-10-17 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 10:23 [PATCH] workqueue: Support RT workqueue Xin Zhao
2025-10-16 15:32 ` Tejun Heo
2025-10-17 9:10 ` Xin Zhao
2025-10-17 15:15 ` Tejun Heo
2025-10-17 15:16 ` Tejun Heo [this message]
2025-10-17 6:19 ` kernel test robot
2025-10-17 6:26 ` Christoph Hellwig
2025-10-17 8:23 ` Xin Zhao
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=aPJd2PggjJwMUs4Q@slm.duckdns.org \
--to=tj@kernel.org \
--cc=jackzxcui1989@163.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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