Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 22 Dec 2022 14:32:52 +0100
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Tudor Ambarus <tudor.ambarus@linaro.org>
Cc:     sashal@kernel.org, corbet@lwn.net, stable@vger.kernel.org,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        joneslee@google.com
Subject: Re: [PATCH] Documentation: stable: Add rule on what kind of patches
 are accepted
Message-ID: <Y6RchEaXUvg+9nKv@kroah.com>
References: <20221222091658.1975240-1-tudor.ambarus@linaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20221222091658.1975240-1-tudor.ambarus@linaro.org>
Precedence: bulk

On Thu, Dec 22, 2022 at 11:16:58AM +0200, Tudor Ambarus wrote:
> The list of rules on what kind of patches are accepted, and which ones
> are not into the “-stable” tree, did not mention anything about new
> features and let the reader use its own judgement. One may be under the
> impression that new features are not accepted at all, but that's not true:
> new features are not accepted unless they fix a reported problem.
> Update documentation with missing rule.
> 
> Link: https://lore.kernel.org/lkml/fc60e8da-1187-ca2b-1aa8-28e01ea2769a@linaro.org/T/#mff820d23793baf637a1b39f5dfbcd9d4d0f0c3a6
> Signed-off-by: Tudor Ambarus <tudor.ambarus@linaro.org>
> ---
>  Documentation/process/stable-kernel-rules.rst | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst
> index 2fd8aa593a28..266290fab1d9 100644
> --- a/Documentation/process/stable-kernel-rules.rst
> +++ b/Documentation/process/stable-kernel-rules.rst
> @@ -22,6 +22,7 @@ Rules on what kind of patches are accepted, and which ones are not, into the
>     maintainer and include an addendum linking to a bugzilla entry if it
>     exists and additional information on the user-visible impact.
>   - New device IDs and quirks are also accepted.
> + - New features are not accepted unless they fix a reported problem.

No need to call this out, it falls under the "fixes a problem" option,
right?

The goal is not to iterate every single option here, that would be
crazy.  Let's keep it short and simple, our biggest problem is that
people do NOT read this document, not that it does not list these types
of corner cases.

So thanks for the patch, but I will not accept it.

thanks,

greg k-h