From: Mark Brown <broonie@debian.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Tejun Heo <tj@kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH v4 0/2] workqueue: Add warnings and check WQ flags usage
Date: Wed, 10 Jun 2026 16:22:15 +0100 [thread overview]
Message-ID: <aimBJ9ClrKXQbl8g@sirena.co.uk> (raw)
In-Reply-To: <bbca08c9-c6bc-4109-b734-14aedc10c93b@I-love.SAKURA.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]
On Wed, Jun 10, 2026 at 09:48:05PM +0900, Tetsuo Handa wrote:
> On 2026/06/02 2:51, Tetsuo Handa wrote:
> > On 2026/06/01 23:47, Tejun Heo wrote:
> > Not all users are quickly accepting patches. Please apply all fixes *before* you start
> > emitting WARNING: message. You are currently making linux-next tree untestable by syzbot.
> > Mark Brown, please skip WQ changes from linux-next until all fixes are applied.
So that's the workqueues tree so extra disruption would be limited but TBH
as far as kicking things out goes I'd be more inclined to take a steer
from Linus on his thinking here rather than making that decision for
myself, especially this close to the merge window. If there's changes
that can't be applied directly to the workqueues tree one thing I could
do that's a bit less disruptive is carry those fixups in -next, do the
appropriate patches exist? We'd obviously need to make sure they get
into mainline promptly.
Just as a note here if you put something at the top of the mail when you
add me it increases my chances of seeing the bit directed at me - I get
CCed on a *lot* of mail that's not at all relevant to me, unfortunately
that means I'm a bit lossy when it comes to triaging my inbox.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-06-10 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260529130640.220328-1-marco.crivellari@suse.com>
[not found] ` <bdce3ef27e358b704541d403d28206fd@kernel.org>
[not found] ` <a808c387-1087-4826-80de-16252ae315b2@I-love.SAKURA.ne.jp>
[not found] ` <a85feb7a94ee487fb5b236d86b674c58@kernel.org>
[not found] ` <5b2dea50-2850-4876-b6e8-ba94b9a85034@I-love.SAKURA.ne.jp>
[not found] ` <ah2bd_V2QHQftm2o@slm.duckdns.org>
2026-06-01 17:51 ` [PATCH v4 0/2] workqueue: Add warnings and check WQ flags usage Tetsuo Handa
2026-06-10 12:48 ` Tetsuo Handa
2026-06-10 15:22 ` Mark Brown [this message]
2026-06-10 17:28 ` Nathan Chancellor
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=aimBJ9ClrKXQbl8g@sirena.co.uk \
--to=broonie@debian.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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