Messages in this thread | | | From | David Brownell <> | Subject | Re: WARN_ON(): proc_dir_entry 'rtc' already registered | Date | Sat, 8 Mar 2008 14:50:48 -0800 |
| |
On Tuesday 19 February 2008, Pavel Machek wrote: > On Mon 2008-02-18 03:08:16, David Brownell wrote: > > On Monday 18 February 2008, Pavel Machek wrote: > > > > How to fix ... how about: instead of just warning folk > > > > off such legacy RTC drivers [1] we just wrap them with > > > > an "if RTC_LIB != n" so this mistake won't be possible. > > > > > > Yes, disabling bad configs in Kconfig seems like way to go. > > > > Problem is ... that also disables valid configs that > > get assembled by picking the right module(s) for the > > target system. > > Is there any reason to use the old rtc subsystem? > > At least OLD_RTC=y NEW_RTC=y should be disabled... even if OLD_RTC=m > NEW_RTC=m makes some sense.
The patch I sent earlier today makes the two mutually exclusive.
Note by the way that there is no OLD_RTC analogue ... just a bunch of individual drivers.
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |