you are arguing against the facts - just look at the report - /dev/rtc
broke and that shouldnt have happened and should be fixed. No amount of
talking you do here will produce a working config.
i have hit 1400 kernel bugs in the past 6 months alone on my
testsystems. That does not mean kernel bugs are the norm and it does not
entitle me to ignore kernel bugs in the future?
uhm, there's no such thing as a "bogus configuration". The Kconfig rules
for RTC (authored by you too) allowed it. If it "makes no sense" it's
because you coded it so - deal with it, it's not hard. But instead of
solving it (it is trivial) you are trying to push the blame to the user
- and that is rather lame to do.
this is not rocket science. The solution is to turn on the fine RTC
code, if the old config option is enabled too. I.e. be more careful
about compatibility. It's still possible to solve this problem and allow
the RTC code to be compiled out completely.
and note that you are hurting users who tried out _your_ RTC code (which
was default off in the past) previously. Yes, while experimenting with
your code they might have created the "wrong" mix of config options but
that's not a problem - this isnt some esoteric embedded platform where
only real men are allowed to configure the kernel and who are left out
in the cold if they mess up - this is Linux where we encourage (and beg)
actual user to test our kernels. So please show some basic respect
towards them and dont arbitrarily declare configs "broken" that were
working in the past.
Ingo
--
