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;
MIME-Version: 1.0
References: <CAH2r5muO1OkOV0jjJo89Zpvj43u_X95smuujg66-emQFgSXfgQ@mail.gmail.com>
 <YwZmu1ZTbjVqIY/C@kroah.com>
In-Reply-To: <YwZmu1ZTbjVqIY/C@kroah.com>
From:   Steve French <smfrench@gmail.com>
Date:   Wed, 24 Aug 2022 13:11:51 -0500
Message-ID: <CAH2r5muu2F3-GiioJsJRdJTbM-gktf0Y8kMFsAD_Evq6a5+DwA@mail.gmail.com>
Subject: Re: "Fixes:" vs. "Cc: stable ..."
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     Stable <stable@vger.kernel.org>,
        LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, Aug 24, 2022 at 12:58 PM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Wed, Aug 24, 2022 at 12:14:12PM -0500, Steve French wrote:
> > Do changesets that already included the "Fixes:" tag in the commit
> > description also need to include the "Cc: stable@vger.kernel.org" in
> > order to be included in stable?
>
> As per the documentation:
>     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>
> You should be putting cc: stable@... on the patch.
>
> But as not all maintainers do, we have to dig through those with Fixes:
> in order to actually catch all bugfixes :(
>
> So please, use cc: stable.

Makes sense - I had noticed a patch which I was going to include in next P/R
which was missing this (fixed now).


-- 
Thanks,

Steve