> And removing a method from an integral, high-level API set is not the
> same as killing static variable in a hardware driver.
removing dead code that nobody is using should be applauded though.
If we left all unused code in the kernel binary we'd soon have a 100Mb
vmlinuz file.... and an unmaintainable mess.
Actively removing parts of the kernel code that nobody is using is a
fight against that bloat (and yes the kernel has grown far too big
already, as I'm sure the handheld.org people already know... you
wouldn't want a 2x bigger vmlinuz right?...
Also, if an API or part of an API is unused, it's quite possibly an API
that SHOULDN'T be used, either because it's designed totally shite (like
sleep_on() is :), because the implementation is really horrid or because
it offers a function that nobody actually needs.
All three are grounds for removal to keep the vmlinuz side down in my
book. That isn't change for change's sake (I'm starting to sound like a
Harry Potter book) but that's an attempt to keep the bloat of the
vmlinuz down.
--
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
-
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]
