From: "Ali Ahmet Memiş" <aliamemis@disroot.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: johannes.goede@oss.qualcomm.com, Len Brown <lenb@kernel.org>,
Armin Wolf <W_Armin@gmx.de>,
Charis Stratakis <c.stratakis@proton.me>,
linux-acpi@vger.kernel.org, linux-pm@vger.kernel.org,
regressions@lists.linux.dev,
Mark Pearson <mpearson-lenovo@squebb.ca>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ACPI: battery: Re-read battery information in the complete callback
Date: Tue, 13 Oct 2026 15:30:52 +0300 [thread overview]
Message-ID: <20261013123055.46306-1-aliamemis@disroot.org> (raw)
In-Reply-To: <CAJZ5v0gS4agVUkCO6M=VW4Wi2y1-s+k23bpzmX9aAZ0Rsv4z9Q@mail.gmail.com>
On Tue, Oct 13, 2026 at 01:58:15PM +0200, Rafael J. Wysocki (Intel) wrote:
> An alternative might be to introduce an "exclusive" variant of
> acpi_evaluate_object() with built-in locking and use it in the cases
> that are known-problematic.
An exclusive variant would have to be used on both sides here, for
_BIX/_BST and for the INT3403 _TMP, since it is \GTST in _TMP that
switches the page. I can do that and test it the same way.
Should this patch still go in for the regression meanwhile?
next prev parent reply other threads:[~2026-10-13 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <37N_jFulf7n-Z55NfKfE71C_wVPxYvZ0xD_iRUg2fXu7TypDiF5PStQ6siSfVBih6fThg5WoPes8U5ZQpfVm_teMFcUGXFxz2DdMbfSWuws=@proton.me>
2026-10-12 22:46 ` Ali Ahmet Memiş
2026-10-12 22:58 ` Ali Ahmet Memiş
2026-10-13 1:40 ` Charis Stratakis
2026-10-13 5:34 ` Ali Ahmet Memiş
2026-10-13 9:33 ` johannes.goede
2026-10-13 11:58 ` Rafael J. Wysocki (Intel)
2026-10-13 12:30 ` Ali Ahmet Memiş [this message]
2026-10-13 13:12 ` Rafael J. Wysocki (Intel)
2026-10-13 13:36 ` johannes.goede
2026-10-13 17:20 ` Rafael J. Wysocki (Intel)
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=20261013123055.46306-1-aliamemis@disroot.org \
--to=aliamemis@disroot.org \
--cc=W_Armin@gmx.de \
--cc=c.stratakis@proton.me \
--cc=johannes.goede@oss.qualcomm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--cc=rafael@kernel.org \
--cc=regressions@lists.linux.dev \
--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
all inboxes | Powered by JetHome®