From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 467182DCC1F for ; Wed, 20 Aug 2025 23:19:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755731986; cv=none; b=smiSwPtHCvtCGAMPMmiSQGp8flMeSXqelQIuK95mQpYcS1SS84uBdHQzv7+Kecz4LtIMdf1NkNS9dsBRGVpvffMfhOnFjCJXdtoftSZSiiabqORtLYV2vpF8RqOpxooIbbKGL7W1J64q8gu7TUnlMG7RGgWksUJacMwG/64sHLU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1755731986; c=relaxed/simple; bh=yZaWdMLAsy4C/5siwNjbC65S7n4WvYketpGJLufA4Hg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Iy971QLHGUZLeo8wTkLATGuP+sfhuxttSAsK6bMxrZmQVtpYwzfxjRQiRRqrEpGHLVnUD+AeqzO29/khVTs9obnUmPUie3MtakZ5KE8RxOfZ/D6X4c5x23A8huJSduKV8LUoN7TuES9OMsZEinn1vE2Ve/zTRL2EnO1KKO+7+8g= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=sO3zEQsr; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="sO3zEQsr" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 979F1C4CEE7; Wed, 20 Aug 2025 23:19:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1755731985; bh=yZaWdMLAsy4C/5siwNjbC65S7n4WvYketpGJLufA4Hg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sO3zEQsrda0tP9MveafyAvfBc3YmlDI6FZTBkBjAlMRdub+/eWp12Eamr5Epw67tV O1NIlMzKSsd58ORDNs8GzqazyJkPq+cKraNBwbz5oKtc9+IcP38S29dPywRro9ShOq WfTHv8Ek2f0/hniu3k3idVm6YdgBmVVQJiJeDmHH/FX+cVt1GY5HvyCw9jTLzYtNcZ W9m/FjrHJL74t2j5jDNCtur6qfi6yPgoknjAfXdTb8It4AfE+V98Hj3Y3VdyqaDDtC 45qWqXRdtIOqH8TrdNDd5UqTD7oE4HJkNk6T+XNvVM2K4OdrohEo22mYGfEf4XuGk+ wrw9w+rb6R8dQ== Date: Wed, 20 Aug 2025 13:19:44 -1000 From: Tejun Heo To: Marco Crivellari Cc: linux-kernel@vger.kernel.org, Lai Jiangshan , Thomas Gleixner , Frederic Weisbecker , Sebastian Andrzej Siewior , Michal Hocko Subject: Re: [PATCH 0/4] Workqueue: replace system wq and change alloc_workqueue callers Message-ID: References: <20250815094510.52360-1-marco.crivellari@suse.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hello, On Tue, Aug 19, 2025 at 02:28:12PM +0200, Marco Crivellari wrote: > Sorry for another email. > > Another question / observation: I guess maintainers can't just pull > the changes and merge for the next release, if the workqueue changes > (e.g. changes in queue_work() etc) are not also merged, right? > > I received a reply here, in the meantime, in "Workqueue: fs: replace > use of system_wq and add WQ_PERCPU to alloc_workqueue users" > (https://www.spinics.net/lists/kernel/msg5811817.html). I can prepare a branch that fs can pull but aren't all the prerequisites already in the master branch from the last cycle? Thanks. -- tejun