[RFC,v2,0/3] wifi locking simplification

Message ID	20230510201205.308542-1-johannes@sipsolutions.net (mailing list archive)
Headers	show Return-Path: <linux-wireless-owner@vger.kernel.org> From: Johannes Berg <johannes@sipsolutions.net> To: linux-kernel@vger.kernel.org Cc: linux-wireless@vger.kernel.org, Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com> Subject: [RFC PATCH v2 0/3] wifi locking simplification Date: Wed, 10 May 2023 22:12:02 +0200 Message-Id: <20230510201205.308542-1-johannes@sipsolutions.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk
Series	wifi locking simplification \| expand [RFC,v2,0/3] wifi locking simplification [RFC,v2,1/3] workqueue: support pausing ordered workqueues [RFC,v2,2/3] wifi: cfg80211: add a workqueue with special semantics [RFC,v2,3/3] wifi: cfg80211: move scan done work to cfg80211 workqueue

Message ID

20230510201205.308542-1-johannes@sipsolutions.net (mailing list archive)

Headers

From: Johannes Berg <johannes@sipsolutions.net>
To: linux-kernel@vger.kernel.org
Cc: linux-wireless@vger.kernel.org, Tejun Heo <tj@kernel.org>,
        Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [RFC PATCH v2 0/3] wifi locking simplification
Date: Wed, 10 May 2023 22:12:02 +0200
Message-Id: <20230510201205.308542-1-johannes@sipsolutions.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Series

wifi locking simplification | expand

Message

Johannes Berg May 10, 2023, 8:12 p.m. UTC

The rationale etc. didn't change in v2, so see
https://lore.kernel.org/r/20230510160428.175409-1-johannes@sipsolutions.net

In v2 I dropped the workqueue locking patch and consequently
made new wiphy_work and wiphy_delayed_work things.

I kept the pause/resume for the workqueue because not that I
had it, it seemed simpler than keeping track of "should it be
paused" in a separate bool variable to not queue the work when
it shouldn't be ...

Still just serves to illustrate things, I didn't really test it.

johannes