linux-kernel - Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1187559950.4419.79.camel@lov.localdomain>
Date:	Sun, 19 Aug 2007 23:45:50 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Atsushi Nemoto <anemo@....ocn.ne.jp>
Cc:	david-b@...bell.net, jengelh@...putergmbh.de, a.zummo@...ertech.it,
	linux-kernel@...r.kernel.org, rtc-linux@...glegroups.com,
	greg@...ah.com
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

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@...y.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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/