From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Linux ACPI" <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Zhang Rui" <rui.zhang@intel.com>,
"Chen Yu" <yu.c.chen@intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
"Linux PCI" <linux-pci@vger.kernel.org>,
"Alex Hung" <alexhung@gmail.com>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
"AceLan Kao" <acelan.kao@canonical.com>
Subject: Re: [PATCH v1] ACPI: scan: Use resource_type() for resource type checking
Date: Fri, 2 Jan 2026 11:56:53 +0000 [thread overview]
Message-ID: <20260102115653.000027f0@huawei.com> (raw)
In-Reply-To: <12814730.O9o76ZdvQC@rafael.j.wysocki>
On Tue, 30 Dec 2025 10:57:34 +0100
"Rafael J. Wysocki" <rafael@kernel.org> wrote:
> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>
> To follow a well-established existing pattern, use resource_type() for
> resource type checking in acpi_scan_claim_resources().
>
> No intentional functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
prev parent reply other threads:[~2026-01-02 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 9:57 [PATCH v1] ACPI: scan: Use resource_type() for resource type checking Rafael J. Wysocki
2025-12-30 11:28 ` Andy Shevchenko
2025-12-30 11:53 ` Ilpo Järvinen
2026-01-02 11:56 ` Jonathan Cameron [this message]
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=20260102115653.000027f0@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=acelan.kao@canonical.com \
--cc=alexhung@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=hansg@kernel.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=yu.c.chen@intel.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