Linux ACPI
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: "EC: Install address space handler at the namespace root" causing issues for some users
Date: Tue, 13 Aug 2024 12:45:11 +0200	[thread overview]
Message-ID: <0e6faf83-d8aa-48aa-a49a-ec28b0d56e8e@redhat.com> (raw)
In-Reply-To: <CAJZ5v0ivbV0h+gmpL+LCUfdDmExjJ1G60jQTzf76iWy6aT0e-Q@mail.gmail.com>

Hi Rafael,

On 8/13/24 12:40 PM, Rafael J. Wysocki wrote:
> Hi,
> 
> On Tue, Aug 13, 2024 at 10:46 AM Hans de Goede <hdegoede@redhat.com> wrote:
>>
>> Hi,
>>
> 
> [cut]
> 
>>
>> The reporter of 2302253 has reported that the patches from:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/log/?h=acpi-ec-fixes
>>
>> resolve the issue; and as mentioned before the reporter of 2298938
>> is not responsive atm. So I believe that with it confirmed that this
>> at least fixes the issues on the LG Gram laptops (1) these patches are
>> ready to be merged now.
> 
> Thanks for the information!
> 
> I'll go ahead and put them into linux-next.

Great. Question is the intention for these to go to Linus
in the 6.12 cycle, or do you just want to let them bake
a bit in linux-next and then plan to send them as a fix
for the 6.11 cycle ?

The reason I'm asking is because the patches these replace
cause a regression on some laptops models starting with 6.9.7
and also all 6.10.y kernels (and if you wait till 6.12,
also all 6.11.y) kernels.

So although this is a somewhat bigger change my personal
preference would be for these to get send out as fixes
and backported to kernels >= 6.9 (1).

Regards,

Hans



1) Just like how the patches they replace end up getting
backported to 6.9.7



> 
>> 1) And based on dmesg with a regressed kernel likely / hopefully also
>> the issue from RH bugzilla 2298938.
>>
> 


  reply	other threads:[~2024-08-13 10:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 11:15 "EC: Install address space handler at the namespace root" causing issues for some users Hans de Goede
2024-07-29 11:29 ` Hans de Goede
2024-07-29 12:20   ` Rafael J. Wysocki
2024-08-01 11:15     ` Hans de Goede
2024-08-01 14:28 ` Hans de Goede
2024-08-05 11:28   ` Hans de Goede
2024-08-05 12:47     ` Hans de Goede
2024-08-08 17:22       ` Rafael J. Wysocki
2024-08-09 13:17         ` Rafael J. Wysocki
2024-08-09 18:02           ` Armin Wolf
2024-08-12 11:34             ` Hans de Goede
2024-08-12 11:28         ` Hans de Goede
2024-08-12 11:31           ` Rafael J. Wysocki
2024-08-13  8:45           ` Hans de Goede
2024-08-13 10:40             ` Rafael J. Wysocki
2024-08-13 10:45               ` Hans de Goede [this message]
2024-08-13 10:53                 ` Rafael J. Wysocki

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=0e6faf83-d8aa-48aa-a49a-ec28b0d56e8e@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@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