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 09:02:00 -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
Subject: Re: [PATCH] rtc: Make rtc-ds1742 driver hotplug-aware

On Friday 17 August 2007, Jan Engelhardt wrote:
> >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.
> >
> Yeah but that does not tell me why it needs the ds1742 alias
> if scripts (whatever they use to discover it) could modprobe rtc-ds1742
> instead.

Because for some reason the driver name isn't rtc-ds1742 ...

My preferred style for such patches puts the MODULE_ALIAS up
near the strange driver name, so it's more clear what's going
on.  Putting all the MODULE_*() stuff at the end of the file
gets confusing in this case.

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