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 41EF61B7E0 for ; Mon, 15 Jan 2024 23:03:12 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Y3Q6RNKY" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 95DE5C433C7; Mon, 15 Jan 2024 23:03:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1705359792; bh=XHEROysl/RUUK/mTAZh0duhwO4dgAjDKyd905jX/FCg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Y3Q6RNKY0FLWNsTegzNyZQqq7kaRST/opUVcKcJjCte1Iaui5tJ+n1l8agGbfu9pm NTxcM7OT3lURVV3Qb8NihgI+bFYhtKQd3m07xmjKUJ68FpJsHlGK1blrbhslCyvdwp Fow+MZBxYV4bwsvRmix+i7plrXdB5smDB9A7m7nVF5dWB0bgQ64oW0mgwfXIypWGzY IEdg0L0Hj/Qd/yOVS2p/O9bM68DcwEhkxO1EXQ5aF+KuLt0hebN6EZAbwId1epo7mG gs05olf27R+R9bbVBJybv/hGhFAsbUL6vz0DYAC4rm+KC6CcEvhm9/B6TwfB2zPtL/ d6rQ9kOMU+ixA== Date: Mon, 15 Jan 2024 18:03:11 -0500 From: Sasha Levin To: Kent Overstreet Cc: stable@vger.kernel.org Subject: Re: fs/bcachefs/ Message-ID: References: Precedence: bulk X-Mailing-List: stable@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: On Mon, Jan 15, 2024 at 05:12:17PM -0500, Kent Overstreet wrote: >Hi stable team - please don't take patches for fs/bcachefs/ except from >myself; I'll be doing backports and sending pull requests after stuff >has been tested by my CI. > >Thanks, and let me know if there's any other workflow things I should >know about Sure, we can ignore fs/bcachefs/ patches. Note that the proposed workflow would only work through patches coming through your tree, but patches in other subsystems that could affect bcachefs might break it in stable trees without being caught by your CI. I'd recommend integrating your pre-release tests with something like kernelci, which would let us catch bcachefs-affecting issues coming from other sources. What more, if we do the above, we could in the future avoid special casing bcachefs :) -- Thanks, Sasha