Linux driver-core infrastructure
 help / color / mirror / Atom feed
From: "Uwe Kleine-König (The Capable Hub)" <u.kleine-koenig@baylibre.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 "Rafael J. Wysocki" <rafael@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>,
	driver-core@lists.linux.dev,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 04/17] driver: core: Include headers for acpi_device_id and of_device_id for struct device_driver
Date: Sat, 27 Jun 2026 17:50:13 +0200	[thread overview]
Message-ID: <aj_wwOo8zuYVlhxn@monoceros> (raw)
In-Reply-To: <CAHk-=whM6kwmSXnD-9pcSNLzvZLFyzXzdm08NuEr-ZH8WxQKPQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]

Hello Linus,

On Fri, Jun 26, 2026 at 11:30:34AM -0700, Linus Torvalds wrote:
> Ok, looking at these patches, I realize that I hate the pathname.
> 
> On Fri, 26 Jun 2026 at 11:01, Uwe Kleine-König (The Capable Hub)
> <u.kleine-koenig@baylibre.com> wrote:
> >
> > +#include <linux/mod_device_id/acpi.h>
> > +#include <linux/mod_device_id/of.h>
> 
> Honestly, that "mod_" part of the path name makes no sense to me.
> 
> Yes, it came from the old header name "mod_devicetable.h", and yes, it
> comes from the fact that the device ID structures are also used for
> module loading rules. So there's a historical reason for the "mod",
> but I don't think it's a particularly good reason, and not a reason to
> keep it.
> 
> None of the structures are called that - they are just called
> "xyz_device_id", and while module loading may be *one* of the uses for
> it, it certainly isn't the only one - or even the main one. Arguably a
> much bigger reason for those device ids tend to be all the bus
> matching code (ie acpi_match_device() and friends).
> 
> So let's just get rid of the "mod" part from the name, ok?

Full ack. I already dropped it in my local tree. I won't resent for that
change now and assume Greg's acks still apply. It will be part of v3
that I intend to send after you cut -rc1.

Thanks
Uwe

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-06-27 15:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26 18:00 [PATCH v2 00/17] mod_devicetable.h: Split into per subsystem headers Uwe Kleine-König (The Capable Hub)
2026-06-26 18:00 ` [PATCH v2 04/17] driver: core: Include headers for acpi_device_id and of_device_id for struct device_driver Uwe Kleine-König (The Capable Hub)
2026-06-26 18:30   ` Linus Torvalds
2026-06-27 15:50     ` Uwe Kleine-König (The Capable Hub) [this message]
2026-06-26 18:35   ` Greg Kroah-Hartman
2026-06-27 16:07 ` [PATCH v2 00/17] mod_devicetable.h: Split into per subsystem headers Danilo Krummrich

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=aj_wwOo8zuYVlhxn@monoceros \
    --to=u.kleine-koenig@baylibre.com \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=torvalds@linux-foundation.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