public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Marco Crivellari <marco.crivellari@suse.com>,
	Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	Frederic Weisbecker <frederic@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Michal Hocko <mhocko@suse.com>
Subject: RE: [PATCH 0/3] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue
Date: Wed, 14 Jan 2026 00:42:21 +0000	[thread overview]
Message-ID: <32088fccfccb468db893b33022f21fba@realtek.com> (raw)
In-Reply-To: <CAAofZF7BkX4hy=Sp2Yjq=aGrYL4wPj_vuoMRxPKpnU2Gs2eQbA@mail.gmail.com>

Marco Crivellari <marco.crivellari@suse.com> wrote:
> On Tue, Jan 13, 2026 at 12:19 PM Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > OK cool, no worries. FWIW I might have even more in wireless-next:
> > https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git/
> >
> > If you want to see what's pending, we have it in patchwork for wireless:
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > The ath6kl one seems to be pending still on Jeff:
> >
> https://patchwork.kernel.org/project/linux-wireless/patch/20251113162032.394804-2-marco.crivellari@sus
> e.com/
> 
> Aha, nice, many thanks!
> 

The rtw88 one [1] is still queued on my hand, because it was wrongly applied [2]
causing regression and reverted by [3]. However, I have not rebased rtw-next
tree on top of wireless tree, so I can't apply [1]. Do you think this is urgent?
If so, I'd send a pull request to wireless-next right now since it is 6.19-rc5.
I don't want frequent pull-request that maintainers have extra load. 

[1] https://patchwork.kernel.org/project/linux-wireless/patch/20251113160605.381777-3-marco.crivellari@suse.com/
[2] 9c194fe4625d ("wifi: rtw88: add WQ_UNBOUND to alloc_workqueue users")
[3] 0ff5e81e1518 ("Revert "wifi: rtw88: add WQ_UNBOUND to alloc_workqueue users"")



  reply	other threads:[~2026-01-14  0:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 16:20 [PATCH 0/3] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-11-13 16:20 ` [PATCH 1/3] ath6kl: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2025-11-13 16:20 ` [PATCH 2/3] cw1200: " Marco Crivellari
2025-11-13 16:20 ` [PATCH 3/3] wifi: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2026-01-13 10:28 ` [PATCH 0/3] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue Marco Crivellari
2026-01-13 11:05   ` Johannes Berg
2026-01-13 11:16     ` Marco Crivellari
2026-01-13 11:19       ` Johannes Berg
2026-01-13 11:24         ` Marco Crivellari
2026-01-14  0:42           ` Ping-Ke Shih [this message]
2026-01-14  9:20             ` Marco Crivellari

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=32088fccfccb468db893b33022f21fba@realtek.com \
    --to=pkshih@realtek.com \
    --cc=bigeasy@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marco.crivellari@suse.com \
    --cc=mhocko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox