From: Tejun Heo <tj@kernel.org>
To: Yu Peng <pengyu@kylinos.cn>
Cc: changlianzhi@uniontech.com, dmitry.torokhov@gmail.com,
gregkh@linuxfoundation.org, jiangshanlai@gmail.com,
jirislaby@kernel.org, legion@kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
lkp@intel.com, mingo@kernel.org, myrrhperiwinkle@qtmlabs.xyz,
oe-lkp@lists.linux.dev, oliver.sang@intel.com,
syzbot+79c403850e6816dc39cf@syzkaller.appspotmail.com,
tglx@linutronix.de
Subject: Re: [PATCH v3 1/2] workqueue: Add initialization macro for work items that disabled by default
Date: Fri, 17 Oct 2025 05:35:45 -1000 [thread overview]
Message-ID: <aPJiUXSVepUgB3OL@slm.duckdns.org> (raw)
In-Reply-To: <20251017075655.3781522-1-pengyu@kylinos.cn>
On Fri, Oct 17, 2025 at 03:56:54PM +0800, Yu Peng wrote:
> In certain scenarios, workqueue tasks that are disabled by default are
> required. Similar to DECLARE_TASKLET_DISABLED, the DECLARE_WORK_DISABLED
> macro is added to achieve this functionality.
>
> Signed-off-by: Yu Peng <pengyu@kylinos.cn>
Applied to wq/for-6.19.
Thanks.
--
tejun
prev parent reply other threads:[~2025-10-17 15:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 13:08 [PATCH] tty/vt: Fix possible deadlock in input_inject_event pengyu
2025-09-29 4:54 ` Dmitry Torokhov
2025-10-01 10:42 ` pengyu
2025-09-30 6:31 ` kernel test robot
2025-10-01 10:23 ` [PATCH v2 1/2] workqueue: Add initialization macro for work items that disabled by default pengyu
2025-10-01 10:23 ` [PATCH v2 2/2] tty/vt: Fix possible deadlock in input_inject_event pengyu
2025-10-07 19:18 ` [PATCH v2 1/2] workqueue: Add initialization macro for work items that disabled by default Tejun Heo
2025-10-17 7:56 ` [PATCH v3 " Yu Peng
2025-10-17 7:56 ` [PATCH v3 2/2] tty/vt: Fix possible deadlock in input_inject_event Yu Peng
2025-10-17 15:35 ` 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=aPJiUXSVepUgB3OL@slm.duckdns.org \
--to=tj@kernel.org \
--cc=changlianzhi@uniontech.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=jirislaby@kernel.org \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=myrrhperiwinkle@qtmlabs.xyz \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=pengyu@kylinos.cn \
--cc=syzbot+79c403850e6816dc39cf@syzkaller.appspotmail.com \
--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
Powered by JetHome