Seems to be only speaking of drivers (the <i>/drivers/android</i> directory, to be specific), which by nature don't need to be part of the kernel itself, hence there is no apparent fork.  That's my understanding, anyway.<p>Not that a fork is really a bad thing, the term has gotten a bad reputation for undeserved reasons.<p>At any rate, gaining acceptance into the main kernel tree can be a big deal for a driver project, but I don't think this is a problem for Android.<p>[edit: looks like I may have read just enough to be dangerous]