From: Kay Sievers <kay.sievers@vrfy.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: david-b@pacbell.net, jengelh@computergmbh.de,
a.zummo@towertech.it, linux-kernel@vger.kernel.org,
rtc-linux@googlegroups.com, greg@kroah.com
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware
Date: Sun, 19 Aug 2007 23:45:50 +0200 [thread overview]
Message-ID: <1187559950.4419.79.camel@lov.localdomain> (raw)
In-Reply-To: <20070819.215751.25908715.anemo@mba.ocn.ne.jp>
On Sun, 2007-08-19 at 21:57 +0900, Atsushi Nemoto wrote:
> On Fri, 17 Aug 2007 18:32:19 +0200, "Kay Sievers" <kay.sievers@vrfy.org> wrote:
> > > I guess there are some out-of-tree users of this driver, but fixing
> > > them is really trivial, so I don't think this is a big compatibility
> > > problem.
> >
> > 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.
>
> I guess your objection is to my usage of MODULE_ALIAS, right?
No, I object to the concept of "platform" to disable all uevents by
default, just to work around its MODALIAS misuse. The rest of the kernel
works properly, and userspace has a unified way to handle events and
module loading.
There is absolutely no reason for "platform" to be different and break
all reasonable assumptions of module-init-tools, udev and HAL.
Thanks,
Kay
next prev parent reply other threads:[~2007-08-19 21:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 16:06 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
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 [this message]
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=1187559950.4419.79.camel@lov.localdomain \
--to=kay.sievers@vrfy.org \
--cc=a.zummo@towertech.it \
--cc=anemo@mba.ocn.ne.jp \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=jengelh@computergmbh.de \
--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
all inboxes | Powered by JetHome®