[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0j4FLDqpQytS5H0OGWwZtdgbAppRwyGfrfyKzzbDqvH6A@mail.gmail.com>
Date: Tue, 12 Aug 2025 21:49:42 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Ilya K <me@...ti.me>, Armin Wolf <W_Armin@....de>, "Rafael J. Wysocki" <rafael@...nel.org>, lenb@...nel.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH] ACPI: EC: Relax sanity check of the ECDT ID string
On Tue, Aug 12, 2025 at 9:33 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>
> On Tue, Aug 12, 2025 at 08:56:55PM +0300, Ilya K wrote:
> > On 2025-08-12 20:10, Greg KH wrote:
> > >
> > > Please read the above link for the full details on how to do this (hint,
> > > Fixes: will not do it.)
> > >
> >
> > I might be missing something, but doesn't that just tell you to CC stable@?
>
> It must be in the patch itself, in the signed-off-by area.
Well, to be precise, it must be present in the mainline commit of that
patch and whether or not it will be there is entirely up to the
committer.
So adding a Cc: stable tag to a patch is a hint, which usually is
appreciated as long as it is accurate, but the committer may still
decide to not include it in the commit.
Powered by blists - more mailing lists