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 84AEE2EC16; Wed, 14 Jun 2023 19:21:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id A389DC433C0; Wed, 14 Jun 2023 19:21:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1686770515; bh=pWxo7CHRl3J5qYPfbEQrjT3qEyGFaT8teEK3o66lcUg=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=dK0Dd7N/nvm9sa9sQ6YFqPCE0djK6abYGeOfqLaAE7OvmGz472hivmfCUPjdts4TH lWlT7vbAcHHsUMba1vj+8aUrfOxPIj68Q1yX2s7UvyUY5mCfQP7WS3UtfxCqlW8fVp C8v2z7HoXukO577ZJcuHlEaFxVfrq+Mo4O2xL5s+pHCFhnK0eWnPV3RWQnRF6kZon3 viVaPiKK9VKLFz5Y5pyaArOm/Lqmy0MkToDVJeYvh4xAEImO9OHI3Sdz7LvsD0djg6 ScEJyEIMlSNvmOehWIE4H3La7znDRQ1o9Vucgt7AyMCnEO1RGlOr9htW/N7lK6Q7D/ EG2L3x/IxylAw== Date: Wed, 14 Jun 2023 12:21:53 -0700 From: Jakub Kicinski To: Kalle Valo Cc: Johannes Berg , Toke =?UTF-8?B?SMO4aWxhbmQt?= =?UTF-8?B?SsO4cmdlbnNlbg==?= , linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, regressions@lists.linux.dev Subject: Re: Closing down the wireless trees for a summer break? Message-ID: <20230614122153.640292b9@kernel.org> In-Reply-To: <87a5x2ccao.fsf@kernel.org> References: <87y1kncuh4.fsf@kernel.org> <871qifxm9b.fsf@toke.dk> <20230613112834.7df36e95@kernel.org> <20230613195136.6815df9b@kernel.org> <87a5x2ccao.fsf@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 14 Jun 2023 18:07:43 +0300 Kalle Valo wrote: > But do note that above is _only_ for -next patches. For patches going to > -rc releases we apply the patches directly to wireless, no other trees > are involved. My proposal was that net maintainers would take only fixes > for -rc releases, my guess from history is that it would be maximum of > 10-15 patches. And once me and Johannes are back we would sort out -next > patches before the merge window. But of course you guys can do whatever > you think is best :) Ah, good note, I would have guessed that fixes go via special trees, too. In that case it should indeed be easy. We'll just look out for maintainer acks on the list and ping people if in doubt.