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]

Date:	Fri, 17 Aug 2007 08:23:15 -0700
From:	David Brownell <david-b@...bell.net>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
Cc:	Atsushi Nemoto <anemo@....ocn.ne.jp>, a.zummo@...ertech.it,
	linux-kernel@...r.kernel.org, rtc-linux@...glegroups.com,
	dbrownell@...rs.sourceforge.net
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Friday 17 August 2007, Jan Engelhardt wrote:
> On Aug 17 2007 01:06, Atsushi Nemoto wrote:
> >Add an MODULE_ALIAS() to make this platform driver hotplug-aware.
> >
> >...
> >+MODULE_ALIAS("ds1742");
> 
> Why exactly is this needed? What script refers to the module as ds1742 instead
> of rtc-ds1742? Regular hotplug (e.g. udev/modprobe) also go by PCI ID or
> whatever is applicable and load the module which provides support for said ID.

Most busses don't have managed device IDs like PCI, USB, or PNP.

The platform, spi, and i2c busses use the driver name, which is
obviously managed within the scope of all Linux drivers.

- Dave
-
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/