From: Tejun Heo <tj@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
kernel-team@meta.com, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH 03/22] IB/hfi1: Use alloc_ordered_workqueue() to create ordered workqueues
Date: Mon, 8 May 2023 15:35:32 -1000 [thread overview]
Message-ID: <ZFmjZCtkuit0MHaI@slm.duckdns.org> (raw)
In-Reply-To: <ZFmMJOdQeku-cND5@slm.duckdns.org>
On Mon, May 08, 2023 at 01:56:20PM -1000, Tejun Heo wrote:
> Applied to wq/for-6.5-cleanup-ordered.
This has WQ_SYSFS so can't be an ordered workqueue. Sorry, this is a pattern
I missed. Dropped the patch.
Thanks.
--
tejun
prev parent reply other threads:[~2023-05-09 1:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230421025046.4008499-1-tj@kernel.org>
2023-04-21 2:50 ` [PATCH 03/22] IB/hfi1: Use alloc_ordered_workqueue() to create ordered workqueues Tejun Heo
2023-04-21 14:02 ` Dennis Dalessandro
2023-05-08 23:56 ` Tejun Heo
2023-05-09 1: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=ZFmjZCtkuit0MHaI@slm.duckdns.org \
--to=tj@kernel.org \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@ziepe.ca \
--cc=jiangshanlai@gmail.com \
--cc=kernel-team@meta.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@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