From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1 0/2] platform/x86: intel: Bind to platform devices instead of ACPI ones
Date: Mon, 09 Mar 2026 16:58:28 +0200 [thread overview]
Message-ID: <177306830893.16654.9099572458213932142.b4-ty@linux.intel.com> (raw)
In-Reply-To: <8692017.NyiUUSuA9g@rafael.j.wysocki>
On Sat, 28 Feb 2026 16:26:44 +0100, Rafael J. Wysocki wrote:
> This series is part of a larger effort to switch over all drivers using
> the struct acpi_driver interface to the more common struct platform_driver
> interface and eliminate the former. The background is explained in
> Documentation/driver-api/acpi/acpi-drivers.rst and in the changelog of
> the patch that introduced the above document:
>
> https://lore.kernel.org/all/2396510.ElGaqSPkdT@rafael.j.wysocki/
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/2] platform/x86: intel/rst: Convert ACPI driver to a platform one
commit: 163a68a31f743c5a820f348322b9162bc89c720a
[2/2] platform/x86: intel/smartconnect: Convert ACPI driver to a platform one
commit: 8a44bd3ffdb269c028236d9165ce06a46c091373
--
i.
prev parent reply other threads:[~2026-03-09 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 15:26 [PATCH v1 0/2] platform/x86: intel: Bind to platform devices instead of ACPI ones Rafael J. Wysocki
2026-02-28 15:27 ` [PATCH v1 1/2] platform/x86: intel/rst: Convert ACPI driver to a platform one Rafael J. Wysocki
2026-02-28 15:28 ` [PATCH v1 2/2] platform/x86: intel/smartconnect: " Rafael J. Wysocki
2026-03-09 14:58 ` Ilpo Järvinen [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=177306830893.16654.9099572458213932142.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--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