From: Tejun Heo <tj@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: 0day robot <lkp@intel.com>, LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH v3] workqueue: Warn flushing of kernel-global workqueues
Date: Mon, 28 Feb 2022 08:42:33 -1000 [thread overview]
Message-ID: <Yh0XmUtuuyaO9j8j@slm.duckdns.org> (raw)
In-Reply-To: <4165db50-1365-549a-eb77-6122c78d4814@I-love.SAKURA.ne.jp>
On Mon, Feb 28, 2022 at 11:03:47PM +0900, Tetsuo Handa wrote:
> Then, what about this?
> If this looks OK, I'll test this patch using linux-next via my tree.
Yeah, looks good to me. Can you boot test and fix the obvious ones before
the pushing it to linux-next? It probably would be best if this is kept in a
separate branch together with all the fix-up patches. Once things settle
enough, we should be able to route the patches through the wq tree to Linus.
Thank you so much for doing this.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: lkp@lists.01.org
Subject: Re: [PATCH v3] workqueue: Warn flushing of kernel-global workqueues
Date: Mon, 28 Feb 2022 08:42:33 -1000 [thread overview]
Message-ID: <Yh0XmUtuuyaO9j8j@slm.duckdns.org> (raw)
In-Reply-To: <4165db50-1365-549a-eb77-6122c78d4814@I-love.SAKURA.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
On Mon, Feb 28, 2022 at 11:03:47PM +0900, Tetsuo Handa wrote:
> Then, what about this?
> If this looks OK, I'll test this patch using linux-next via my tree.
Yeah, looks good to me. Can you boot test and fix the obvious ones before
the pushing it to linux-next? It probably would be best if this is kept in a
separate branch together with all the fix-up patches. Once things settle
enough, we should be able to route the patches through the wq tree to Linus.
Thank you so much for doing this.
--
tejun
next prev parent reply other threads:[~2022-02-28 18:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 8:33 [workqueue] 29bd199e4e: WARNING:possible_circular_locking_dependency_detected kernel test robot
2022-02-21 8:33 ` kernel test robot
2022-02-21 10:38 ` [PATCH] workqueue: Use private WQ for schedule_on_each_cpu() API Tetsuo Handa
2022-02-21 10:38 ` Tetsuo Handa
2022-02-22 17:29 ` Tejun Heo
2022-02-22 17:29 ` Tejun Heo
2022-02-23 0:57 ` Tetsuo Handa
2022-02-23 0:57 ` Tetsuo Handa
2022-02-23 21:33 ` Tejun Heo
2022-02-23 21:33 ` Tejun Heo
2022-02-23 22:26 ` Tetsuo Handa
2022-02-23 22:26 ` Tetsuo Handa
2022-02-23 22:29 ` Tejun Heo
2022-02-23 22:29 ` Tejun Heo
2022-02-28 14:03 ` [PATCH v3] workqueue: Warn flushing of kernel-global workqueues Tetsuo Handa
2022-02-28 14:03 ` Tetsuo Handa
2022-02-28 18:42 ` Tejun Heo [this message]
2022-02-28 18:42 ` Tejun Heo
2022-03-17 22:25 ` Tetsuo Handa
2022-03-17 22:25 ` Tetsuo Handa
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=Yh0XmUtuuyaO9j8j@slm.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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.