The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Rafael J.  Wysocki" <rafael@kernel.org>
Cc: "Linux ACPI" <linux-acpi@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Hans de Goede" <hansg@kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Linux Documentation" <linux-doc@vger.kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	driver-core@lists.linux.dev
Subject: Re: [PATCH v1 1/2] 1/2] ACPI: bus: Eliminate struct acpi_driver
Date: Fri, 03 Jul 2026 22:37:03 +0200	[thread overview]
Message-ID: <DJP83RJ4N7HN.2ZT3XI74J62GN@kernel.org> (raw)
In-Reply-To: <5132944.31r3eYUQgx@rafael.j.wysocki>

On Wed Jul 1, 2026 at 9:16 PM CEST, Rafael J.  Wysocki wrote:
> From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
>
> Now that struct acpi_driver has no more users, eliminate it along with
> all of the code related to it.
>
> Also remove the file added by commit b8c8a8ea18ad ("ACPI: Documentation:
> driver-api: Disapprove of using ACPI drivers") because it will not be
> necessary any more after eliminating struct acpi_driver from the code.
>
> No intentional functional impact.
>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>

Reviewed-by: Danilo Krummrich <dakr@kernel.org>

  reply	other threads:[~2026-07-03 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 19:15 [PATCH v1 0/2] ACPI: bus: Remove struct acpi_driver from the kernel Rafael J. Wysocki (Intel)
2026-07-01 19:16 ` [PATCH v1 1/2] 1/2] ACPI: bus: Eliminate struct acpi_driver Rafael J.  Wysocki
2026-07-03 20:37   ` Danilo Krummrich [this message]
2026-07-01 19:17 ` [PATCH v1 2/2] ACPI: scan: Set power.no_pm for all struct acpi_device objects Rafael J.  Wysocki
2026-07-03 20:37   ` Danilo Krummrich
2026-07-02  9:15 ` [PATCH v1 0/2] ACPI: bus: Remove struct acpi_driver from the kernel Andy Shevchenko
2026-07-02 11:31   ` Rafael J. Wysocki (Intel)

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=DJP83RJ4N7HN.2ZT3XI74J62GN@kernel.org \
    --to=dakr@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@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=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