Greg K-H

@gregkh @imalchev Could you disclose why the choice of stable-ABI GKI over DKMS-style GKI has been made for Android? This feels like a net loss in term of kernel maintenance, of access to source code for the OSS community, and of running/certifying Android close to mainline.

What do you mean by "DKMS-style GKI"? And how is this a net loss?

A Linux kernel that includes its own Linux headers (as has been proposed on LKML), and modules gets built on startup (or on upgrade). I consider it a net loss, because as LKMs were historically forbidden in Android, GPL meant we got sources of all kernel-space.

With ABI-stable GKI, OEMs can just answer "Kernel sources are available at https://android.googlesource.com/kernel/common "

Yes, if they wanted to, and somehow thought that this meets the license requirements of the GPL (hint, I doubt it.) They still have to provide source of their kernel modules, as they do today, nothing has changed here at all with that.