* Michael Buesch <[email protected]> wrote:
> In my opinion this all is the work of the distributions and not the
> work of the kernel developers. Distributions have to make sure that
> everything works after a kernel update. [...]
actually, not. The the task of kernel developers is to KEEP OLD
DISTRIBUTIONS WORKING WITH NEW DRIVERS. Or the "old" driver stays around
until eternity, because the new one is just BROKEN.
Take a look at CONFIG_COMPAT_VDSO for example - one single version of
glibc was released in a distro that depended on a kernel vDSO bug. So
we'll keep that aspect of the vDSO perhaps forever. Simple as that.
Stuff must just work. Whatever it takes. Best is if you add in new stuff
without the user noticing _ANYTHING_ but that the kernel version bumped.
If the maintainers of the other 7 million lines of kernel code can get
this right then the wireless code should be able to do it too. Ok?
all this "distributors will have to sort out the mess" talk is nonsense,
and i really hope you do not truly believe in that crap. If your
attitude is prevalent in the wireless development community then it's in
worse shape than i thought :-(
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
