public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@just42.net>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Robert Gerlach" <khnz@gmx.de>,
	"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/5] platform/x86: fujitsu: Bind drivers to platform devices instead of ACPI ones
Date: Tue, 3 Mar 2026 00:09:07 +1030	[thread overview]
Message-ID: <aaWS+4jXPfec5fTG@marvin.atrad.com.au> (raw)
In-Reply-To: <1968442.tdWV9SEqCh@rafael.j.wysocki>

Hi Rafael

On Wed, Feb 25, 2026 at 09:41:09PM +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/
> 
> The bottom line is that the kernel would be better off without struct
> acpi_driver and so it is better to get rid of it.
> 
> This series carries out driver conversions of the platform x86 drivers
> for Fujitsu platforms.
> 
> Patch [1/5] converts the fujitsu-tablet to a proper platform one based
> on the struct platform_driver interface.
> 
> Patch [2/5] rearranges the code in the fujitsu-laptop driver to avoid
> introducing forward declarations of some functions in the subsequent
> patches.
> 
> Patch [3/5] updates the fujitsu-laptop driver to install ACPI notify
> handlers by itself instead of using .notify() callbacks from struct
> acpi_driver, which is requisite for the driver conversion.
> 
> Patches [4-5/5] replaces two instances of the struct acpi_driver
> interface in the fujitsu-laptop driver with struct platform_driver.

Thanks for preparing this patch series.  It looks reasonable to me.  At this
point I have nothing to add.

Acked-by: Jonathan Woithe <jwoithe@just42.net>

Regards
  jonathan

      parent reply	other threads:[~2026-03-02 13:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 20:41 [PATCH v1 0/5] platform/x86: fujitsu: Bind drivers to platform devices instead of ACPI ones Rafael J. Wysocki
2026-02-25 20:42 ` [PATCH v1 1/5] platform/x86: fujitsu-tablet: Convert ACPI driver to a platform one Rafael J. Wysocki
2026-02-25 20:43 ` [PATCH v1 2/5] platform/x86: fujitsu: Reorder code to avoid forward declarations Rafael J. Wysocki
2026-02-25 20:47 ` [PATCH v1 3/5] platform/x86: fujitsu: Register ACPI notify handlers directly Rafael J. Wysocki
2026-03-09 13:00   ` Ilpo Järvinen
2026-03-09 16:12     ` Rafael J. Wysocki
2026-03-09 16:17       ` Ilpo Järvinen
2026-03-09 16:24         ` Rafael J. Wysocki
2026-02-25 20:52 ` [PATCH v1 4/5] platform/x86: fujitsu: Convert backlight driver to a platform one Rafael J. Wysocki
2026-02-25 20:57 ` [PATCH v1 5/5] platform/x86: fujitsu: Convert laptop " Rafael J. Wysocki
2026-03-02 13:39 ` Jonathan Woithe [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=aaWS+4jXPfec5fTG@marvin.atrad.com.au \
    --to=jwoithe@just42.net \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=khnz@gmx.de \
    --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