From: Armin Wolf <W_Armin@gmx.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ilya K <me@0upti.me>, "Rafael J. Wysocki" <rafael@kernel.org>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ACPI: EC: Relax sanity check of the ECDT ID string
Date: Wed, 13 Aug 2025 00:27:08 +0200 [thread overview]
Message-ID: <f4de859e-3cbc-403b-b9da-12a426ba6a74@gmx.de> (raw)
In-Reply-To: <2025081227-humpback-garden-7a4b@gregkh>
Am 12.08.25 um 19:10 schrieb Greg KH:
> On Tue, Aug 12, 2025 at 06:54:39PM +0200, Armin Wolf wrote:
>> Am 12.08.25 um 18:40 schrieb Greg KH:
>>
>>> On Tue, Aug 12, 2025 at 06:51:10PM +0300, Ilya K wrote:
>>>> On 2025-08-12 16:32, Rafael J. Wysocki wrote:
>>>>> Applied as 6.17-rc material and sorry for the delay (I was offline).
>>>>>
>>>>> Thanks!
>>>> Thanks!
>>>>
>>>> Tagging stable@ so we're hopefully in time for 6.16.1.
>>> <formletter>
>>>
>>> This is not the correct way to submit patches for inclusion in the
>>> stable kernel tree. Please read:
>>> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
>>> for how to do this properly.
>>>
>>> </formletter>
>> Agree.
>>
>> AFAIK the Fixes: tag should be enough to ensure that this patch gets included
>> in the affected stable kernels.
> Not at all!
>
> Please read the above link for the full details on how to do this (hint,
> Fixes: will not do it.)
>
> thanks,
>
> greg k-h
Oops, seems that i missed something rather significant about the stable kernels.
I will give keep that in mind when sending future patches.
Thanks,
Armin Wolf
prev parent reply other threads:[~2025-08-12 22:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 6:20 [PATCH] ACPI: EC: Relax sanity check of the ECDT ID string Armin Wolf
2025-07-29 7:00 ` Ilya K
2025-07-30 16:49 ` Armin Wolf
2025-07-30 16:59 ` Ilya K
2025-07-30 17:38 ` Armin Wolf
2025-08-05 16:40 ` Ilya K
2025-08-12 13:32 ` Rafael J. Wysocki
2025-08-12 15:51 ` Ilya K
2025-08-12 16:40 ` Greg KH
2025-08-12 16:54 ` Armin Wolf
2025-08-12 17:10 ` Greg KH
2025-08-12 17:56 ` Ilya K
2025-08-12 18:38 ` Rafael J. Wysocki
2025-08-12 19:31 ` Greg KH
2025-08-12 19:49 ` Rafael J. Wysocki
2025-08-12 22:27 ` Armin Wolf [this message]
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=f4de859e-3cbc-403b-b9da-12a426ba6a74@gmx.de \
--to=w_armin@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@0upti.me \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.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