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:   Tue, 11 Jul 2023 10:42:41 +0200
From:   Johan Hovold <johan@kernel.org>
To:     Thorsten Leemhuis <linux@leemhuis.info>
Cc:     Greg KH <gregkh@linuxfoundation.org>, stable@vger.kernel.org,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
        Sasha Levin <sashal@kernel.org>,
        Jonathan Corbet <corbet@lwn.net>
Subject: Re: [RFC PATCH v1 0/3] docs: stable-kernel-rules: add delayed
 backporting option and a few tweaks
Message-ID: <ZK0WAbB2P8wFWPCu@hovoldconsulting.com>
References: <cover.1689008220.git.linux@leemhuis.info>
 <29fb398b-a81c-70f9-f67c-21daaa42e4f7@leemhuis.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <29fb398b-a81c-70f9-f67c-21daaa42e4f7@leemhuis.info>
Precedence: bulk

On Mon, Jul 10, 2023 at 07:18:43PM +0200, Thorsten Leemhuis wrote:
> On 10.07.23 19:10, Thorsten Leemhuis wrote:

> >  * For patches that may have kernel version prerequisites specify them using
> >    the following format in the sign-off area:
> > 
> >    .. code-block:: none
> > 
> >      Cc: <stable@vger.kernel.org> # 3.3.x
> > 
> >    The tag has the meaning of:
> > 
> >    .. code-block:: none
> > 
> >      git cherry-pick <this commit>
> > 
> >    For each "-stable" tree starting with the specified version.
> 
> /me wonders if something like a "note, such tagging is unnecessary if
> the appropriate version can be derived from a Fixes: tag" would be
> appropriate and worth it here

Having these comments in the patch itself makes it easier to determine
whether a fix addresses a recent regression or an issue that's been
around since forever without having to copy-paste and look up each
commit in the Fixes tag(s).

Johan