linux-kernel - Re: Kconfig RTC selection (was: 2.6.25-rc7: Ugh.)

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 for Android: free password hash cracker in your pocket

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

Date:	Fri, 28 Mar 2008 15:18:35 -0700
From:	David Brownell <david-b@...bell.net>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Mark Lord <lkml@....ca>, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, rtc-linux@...glegroups.com,
	David Miller <davem@...emloft.net>
Subject: Re: Kconfig RTC selection (was: 2.6.25-rc7: Ugh.)

On Friday 28 March 2008, Adrian Bunk wrote:

> > > grep for CONFIG_SUN_MOSTEK_RTC and you'll get the point.
> > 
> > Right:  it doesn't mention JS_RTC at all.  Whatever is up
> > with that stuff, it's broken.
> 
> You miss the point, the point is:
>   drivers/sbus/char/Makefile:obj-$(CONFIG_SUN_MOSTEK_RTC) += rtc.o
> 
> Two modules with the same name in one build are not allowed.

It gets uglier and uglier.  So if that abortion is really
needed, it'd make more sense to rename the MOSTEK code.
If that's not fixed, its Kconfig should mention needing
the JS_RTC thing instead of the "real" legacy rtc.c ...

Glad I got rid of my JavaStation ages ago, but I liked
the idea of having a real builtin coffee cup holder.  :)

You see why nobody wants to touch the legacy RTC stuff?
Some of it is broken *BY DESIGN* instead of just by
pure happenstance of evolution.

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