From: Nathan Chancellor <nathan@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Tejun Heo <tj@kernel.org>, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>,
Marco Crivellari <marco.crivellari@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: Drop WQ_PERCPU from ordered_flags in btrfs_init_workqueues()
Date: Fri, 5 Jun 2026 09:06:17 -0700 [thread overview]
Message-ID: <20260605160617.GA3477552@ax162> (raw)
In-Reply-To: <aiKNJN8w9Zq2s-Zy@gmail.com>
On Fri, Jun 05, 2026 at 01:48:24AM -0700, Breno Leitao wrote:
> On Thu, Jun 04, 2026 at 02:58:11PM -0700, Nathan Chancellor wrote:
> > Could you please pick up this patch for -next to clear up this warning?
> > Not sure if this was on your radar since it is a btrfs change.
>
> Why not getting this through the btrfs tree, given this is a btrfs
> change?
The warning is only visible after commit 21c05ca88a54 ("workqueue: Add
warnings and ensure one among WQ_PERCPU or WQ_UNBOUND is present") in
the workqueue tree. If it goes via the btrfs tree, there could be a
period during the merge window where the warning appears if the
workqueue tree is merged before the btrfs tree. Not the biggest deal
since it is a runtime warning but there are already other patches in the
workqueue tree that avoid warnings and David already provided an Ack, so
I don't see a reason to deviate from the proper process here. Up to
Tejun and the btrfs folks though.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-06-05 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 2:46 [PATCH] btrfs: Drop WQ_PERCPU from ordered_flags in btrfs_init_workqueues() Nathan Chancellor
2026-06-02 13:16 ` David Sterba
2026-06-02 15:40 ` Marco Crivellari
2026-06-04 9:52 ` Breno Leitao
2026-06-04 21:58 ` Nathan Chancellor
2026-06-05 8:48 ` Breno Leitao
2026-06-05 16:06 ` Nathan Chancellor [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=20260605160617.GA3477552@ax162 \
--to=nathan@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=leitao@debian.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=tj@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 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.