From: David Brownell <david-b@pacbell.net>
To: "Kay Sievers" <kay.sievers@vrfy.org>
Cc: "Atsushi Nemoto" <anemo@mba.ocn.ne.jp>,
jengelh@computergmbh.de, a.zummo@towertech.it,
linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
"Greg KH" <greg@kroah.com>
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware
Date: Fri, 17 Aug 2007 09:55:05 -0700 [thread overview]
Message-ID: <200708170955.06388.david-b@pacbell.net> (raw)
In-Reply-To: <3ae72650708170932y5369213bq3479708216923edb@mail.gmail.com>
On Friday 17 August 2007, Kay Sievers wrote:
> Again,
"Again"?
> the only sane solution is to provide MODALIAS="platform:<name>"
> from the platform bus, and adding the aliases to drivers who support
> autoloading. Modalias strings are not free-text strings, they are
> required to be prefixed by the subsystem.
If so, then whoever tried to change the usage of module aliases
in that way goofed in several ways. First, by not changing all
the in-kernel uses. Second, by not changing all the out-of-tree
uses in various distros, toolchains, etc. Third, by not even
documenting that change...
Module aliases have been around since very early versions of
stuff like "modprobe" ... without that new rule. Aliases have
always been
> I still fail to see why platform must be different from everything
> else in the kernel.
It isn't. See above.
> Please change that stuff, and the bugs which we
> are fighting magically go away, because module-init-tools alias
> resolving works like it does for every other subsystem in the kernel.
Those bugs would be ... what? "We" haven't observed anything
attributable to this usage, which has been common for years now.
- Dave
next prev parent reply other threads:[~2007-08-17 16:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 16:06 [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware Atsushi Nemoto
2007-08-17 10:59 ` Jan Engelhardt
2007-08-17 15:23 ` David Brownell
2007-08-17 15:37 ` Jan Engelhardt
2007-08-17 16:02 ` David Brownell
2007-08-17 16:15 ` Atsushi Nemoto
2007-08-17 16:26 ` David Brownell
2007-08-17 16:32 ` Kay Sievers
2007-08-17 16:55 ` David Brownell [this message]
2007-08-17 17:18 ` Kay Sievers
2007-08-17 19:50 ` David Brownell
2007-08-17 19:52 ` Jan Engelhardt
2007-08-17 20:20 ` David Brownell
2007-08-18 2:40 ` Kay Sievers
2007-08-18 4:06 ` David Brownell
2007-08-18 10:45 ` Kay Sievers
2007-08-20 1:44 ` legacy platform drivers and hotplugging David Brownell
2007-08-20 2:02 ` Atsushi Nemoto
2007-08-20 9:51 ` Kay Sievers
2007-08-19 12:57 ` [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware Atsushi Nemoto
2007-08-19 21:45 ` Kay Sievers
2007-08-20 1:48 ` David Brownell
2007-08-20 2:02 ` David Brownell
2007-08-20 2:16 ` Atsushi Nemoto
2007-08-17 16:04 ` Atsushi Nemoto
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=200708170955.06388.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=a.zummo@towertech.it \
--cc=anemo@mba.ocn.ne.jp \
--cc=greg@kroah.com \
--cc=jengelh@computergmbh.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
/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