All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki (Intel)" <rafael@kernel.org>
Cc: Danilo Krummrich <dakr@kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Driver Core Development <driver-core@lists.linux.dev>
Subject: Re: [PATCH v2] driver core/ACPI: Introduce companion_bus_register()
Date: Wed, 16 Sep 2026 19:52:54 +0100	[thread overview]
Message-ID: <2026091644-shiftless-armchair-a429@gregkh> (raw)
In-Reply-To: <CAJZ5v0geju99B56CqAQjKwZcwg7mqXPUxx_a=kQ1KpaKpQztuw@mail.gmail.com>

On Wed, Sep 16, 2026 at 08:45:50PM +0200, Rafael J. Wysocki (Intel) wrote:
> On Wed, Sep 9, 2026 at 6:41 PM Rafael J. Wysocki <rafael@kernel.org> wrote:
> >
> > From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >
> > The ACPI bus type does not allow drivers to be registered, so the sysfs
> > attributes related to drivers created for it and its devices are
> > useless, and its drivers/ directory is always empty.  All of that is
> > confusing and wasteful.
> >
> > To allow skipping the creation of those sysfs attributes, introduce a
> > "companion" bus type concept and add a special registration function for
> > registering "companion" bus types, companion_bus_register().
> >
> > Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> It's been a while since this was posted, so any feedback would be appreciated.
> 
> In the absence thereof, I'll trust Sashiko that there are no issues
> with it and pick it up.

Looks sane:

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  reply	other threads:[~2026-09-16 18:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 16:41 [PATCH v2] driver core/ACPI: Introduce companion_bus_register() Rafael J. Wysocki
2026-09-16 18:45 ` Rafael J. Wysocki (Intel)
2026-09-16 18:52   ` Greg Kroah-Hartman [this message]
2026-09-16 18:51 ` Danilo Krummrich
2026-09-23 17:05 ` Michael Kelley
2026-09-23 17:32   ` Rafael J. Wysocki (Intel)
2026-09-23 18:31     ` Rafael J. Wysocki (Intel)
2026-09-23 18:50       ` Rafael J. Wysocki (Intel)
2026-09-23 19:11         ` Rafael J. Wysocki (Intel)
2026-09-24 18:23   ` Michael Kelley
2026-09-24 18:44     ` Rafael J. Wysocki (Intel)
2026-09-24 21:47       ` Michael Kelley
2026-09-25  9:08         ` Rafael J. Wysocki (Intel)
2026-09-29  3:51           ` Michael Kelley

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=2026091644-shiftless-armchair-a429@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=linux-acpi@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 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.