From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <helgaas@kernel.org>,
Hans de Goede <hansg@kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Zhang Rui <rui.zhang@intel.com>, Armin Wolf <w_armin@gmx.de>,
Danilo Krummrich <dakr@kernel.org>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v1] ACPI: Documentation: driver-api: Disapprove of using ACPI drivers
Date: Mon, 5 Jan 2026 17:50:41 +0200 [thread overview]
Message-ID: <aVvd0eYC7Qs5_ZdD@smile.fi.intel.com> (raw)
In-Reply-To: <2026010553-capable-chip-88d7@gregkh>
On Mon, Jan 05, 2026 at 02:47:30PM +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 05, 2026 at 12:25:04PM +0100, Rafael J. Wysocki wrote:
> Documenting this is fine, but really, just moving all of the existing
> drivers to not use this and deleting the api entirely might be simplest.
> Looks like the only "new" acpi drivers that show up are in the
> platform/x86/ subsystem, so just tell the maintainers there not to take
> any new ones?
I believe that with or without documentation this will take a few cycles
to get rid of (as there are more than just the PDx86 being involved as of
today). Also there were (and might be in the future) a few attempts to convert
in the opposite direction, i.e. from platform to ACPI driver. Doing something
temporary for a few cycles is okay, no? From my point of view it helps avoiding
the above mentioned cases.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-05 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 11:25 [PATCH v1] ACPI: Documentation: driver-api: Disapprove of using ACPI drivers Rafael J. Wysocki
2026-01-05 13:47 ` Greg Kroah-Hartman
2026-01-05 15:50 ` Andy Shevchenko [this message]
2026-01-05 16:47 ` Armin Wolf
2026-01-05 17:53 ` Rafael J. Wysocki
2026-01-05 15:45 ` Andy Shevchenko
2026-01-05 18:44 ` Rafael J. Wysocki
2026-01-05 16:51 ` Armin Wolf
2026-01-05 19:40 ` Randy Dunlap
2026-01-05 19:59 ` Rafael J. Wysocki
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=aVvd0eYC7Qs5_ZdD@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=w_armin@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.