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
Date: Thu, 22 Dec 2022 14:32:52 +0100 [thread overview]
Message-ID: <Y6RchEaXUvg+9nKv@kroah.com> (raw)
In-Reply-To: <20221222091658.1975240-1-tudor.ambarus@linaro.org>
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
next prev parent reply other threads:[~2022-12-22 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 9:16 [PATCH] Documentation: stable: Add rule on what kind of patches are accepted Tudor Ambarus
2022-12-22 12:56 ` Bagas Sanjaya
2022-12-22 13:01 ` Tudor Ambarus
2022-12-23 1:55 ` Bagas Sanjaya
2022-12-22 13:32 ` Greg KH [this message]
2022-12-22 14:20 ` Tudor Ambarus
2022-12-22 16:24 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y6RchEaXUvg+9nKv@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=corbet@lwn.net \
--cc=joneslee@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox