From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Linux ACPI <linux-acpi@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v1] ACPI: scan: Clean up after recent changes
Date: Sat, 10 Jan 2026 12:50:54 +0100 [thread overview]
Message-ID: <12825056.O9o76ZdvQC@rafael.j.wysocki> (raw)
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Use LIST_HEAD() for initializing an on-stack list head in two places and
remove an empty code line added by mistake.
No intentional functional impact.
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
---
This is based on ACPI changes in linux-next.
---
drivers/acpi/acpi_platform.c | 2 +-
drivers/acpi/scan.c | 3 +--
2 files changed, 2 insertions(+), 3 deletions(-)
--- a/drivers/acpi/acpi_platform.c
+++ b/drivers/acpi/acpi_platform.c
@@ -136,7 +136,7 @@ struct platform_device *acpi_create_plat
}
if (adev->device_type == ACPI_BUS_TYPE_DEVICE && !adev->pnp.type.backlight) {
- struct list_head resource_list = LIST_HEAD_INIT(resource_list);
+ LIST_HEAD(resource_list);
count = acpi_dev_get_resources(adev, &resource_list, NULL, NULL);
if (count < 0)
--- a/drivers/acpi/scan.c
+++ b/drivers/acpi/scan.c
@@ -2602,8 +2602,8 @@ static void acpi_scan_postponed(void)
static void acpi_scan_claim_resources(struct acpi_device *adev)
{
- struct list_head resource_list = LIST_HEAD_INIT(resource_list);
struct resource_entry *rentry;
+ LIST_HEAD(resource_list);
unsigned int count = 0;
const char *regionid;
@@ -2660,7 +2660,6 @@ exit:
acpi_dev_free_resource_list(&resource_list);
}
-
static int __init acpi_reserve_motherboard_resources(void)
{
struct acpi_scan_system_dev *sd, *tmp;
next reply other threads:[~2026-01-10 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 11:50 Rafael J. Wysocki [this message]
2026-01-10 13:25 ` Mario Limonciello (AMD) (kernel.org)
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=12825056.O9o76ZdvQC@rafael.j.wysocki \
--to=rafael@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
/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®