This is not correct, you don't understand how the gpl works, or how linking works wrt license compliance, nor do you understand the kernels approach to GPL compliance and linking.
The real problem is that I could point you to source.google.com and you could download the kernel and other gpl components from honeycomb right this second, but kernel.org and the osuosl site is recovering from a nasty hack. When those machines are back up, I invite you to go get the code you seem to be interested in.
> you don't understand how the gpl works, or how linking works wrt license compliance
Please clarify. Am I allowed to statically link GPL code with closed-source code and distribute resulting collective work in binary form? Am I allowed to dynamically link GPL code with closed-source code and distribute resulting collective work in binary form?
If the answer for the second question is "yes", what's the difference between GPL and LGPL then?
The real problem is that I could point you to source.google.com and you could download the kernel and other gpl components from honeycomb right this second, but kernel.org and the osuosl site is recovering from a nasty hack. When those machines are back up, I invite you to go get the code you seem to be interested in.