mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leonard Lausen <leonard@lausen.nl>
To: Armin Wolf <W_Armin@gmx.de>,
	linux-acpi@vger.kernel.org,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Maciej Wieczor-Retman <maciej.wieczor-retman@intel.com>,
	Pawel Chmielewski <pawel.chmielewski@intel.com>,
	acpica-devel@lists.linux.dev, Len Brown <lenb@kernel.org>,
	Ivan Hu <ivan.hu@canonical.com>,
	Joshua Grisham <josh@joshuagrisham.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] ACPI: fan: Ignore broken _FST on Samsung Galaxy Book 930XDB
Date: Tue, 3 Nov 2026 13:13:28 +0100	[thread overview]
Message-ID: <88ccf8fa-be8d-46cb-b0ba-87e94b50a49c@lausen.nl> (raw)
In-Reply-To: <35c80ebb-fb5c-45cd-b6e9-d6b73e305432@gmx.de>

> This is very likely connected to https://github.com/open-acpica/acpica/ 
> issues/908. The ACPI spec says that Increment/Decrement is "Equivalent 
> to Add (Addend, 1, Addend)", so i suspect that Add() should try to 
> automatically dereference the reference.
> 
> I would suggest that you report this issue to the ACPICA guys instead.

Thank you for the pointer, Armin. Maciej and me fixed the issue in 
ACPICA and it is now in upstream pending branch. 
https://github.com/open-acpica/acpica/commit/8854b938571e4f780c2673b3f7df440694ac4229 
I'm not sure when it will make it's way to the kernel.

Best regards
Leonard

  reply	other threads:[~2026-11-03 12:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 14:54 [PATCH 0/3] ACPI: Work around Samsung Galaxy Book 930XDB firmware errors Leonard Lausen
2026-10-19 14:54 ` [PATCH 1/3] ACPICA: Initialize ParserState.AmlEnd in AcpiInstallMethod Leonard Lausen
2026-10-22 18:10   ` Rafael J. Wysocki (Intel)
2026-10-19 14:54 ` [PATCH 2/3] ACPI: fan: Ignore broken _FST on Samsung Galaxy Book 930XDB Leonard Lausen
2026-10-22 18:31   ` Armin Wolf
2026-11-03 12:13     ` Leonard Lausen [this message]
2026-10-19 14:54 ` [PATCH 3/3] ACPI: x86: Repair broken PEG0._STA " Leonard Lausen

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=88ccf8fa-be8d-46cb-b0ba-87e94b50a49c@lausen.nl \
    --to=leonard@lausen.nl \
    --cc=W_Armin@gmx.de \
    --cc=acpica-devel@lists.linux.dev \
    --cc=ivan.hu@canonical.com \
    --cc=josh@joshuagrisham.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=pawel.chmielewski@intel.com \
    --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
all inboxes | Powered by JetHome®