Received-SPF: pass (google.com: domain of linux-kernel+bounces-81934-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux ACPI <linux-acpi@vger.kernel.org>,
 Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
 Mika Westerberg <mika.westerberg@linux.intel.com>,
 "Rafael J. Wysocki" <rafael@kernel.org>,
 "Russell King (Oracle)" <linux@armlinux.org.uk>
Subject:
 [PATCH v2 0/5] ACPI: scan: Check enabled _STA bit on Bus/Device Checks
Date: Mon, 26 Feb 2024 17:24:57 +0100
Message-ID: <6021126.lOV4Wx5bFT@kreacher>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="UTF-8"

Hi,

This is an update of the patch series at

https://lore.kernel.org/linux-acpi/4562925.LvFx2qVVIh@kreacher/

which mostly only rearranges the code and makes one functional
change in acpi_scan_devie_check().

The original series description is mostly still applicable:

"This series adds _STA enabled bit checking for processors (in all cases)
 and for all devices in the Bus Check and Device Check notification handling
 paths.  It does so without any side-effects on non-processor devices, unlike

 https://lore.kernel.org/linux-acpi/E1rVDmP-0027YJ-EW@rmk-PC.armlinux.org.uk/

 The first patch fixes an issue with failing Device Check notifications
 without a valid reason.

 The next two patches together make Bus Check and Device Check notification
 handling take the enabled bit into account.

 The last patch modifies the processor scan handler to check the enabled bit
 it its add callback.

 I would appreciate testing this on a system where the enabled bit really
 matters."

Thanks!