[for_xyz]

> They can just ship a custom kernel only to their users and leave it at that.

Works really well for Google and Android where they offload handpicked versions of the Linux kernel to the phone vendors to maintain. In practice they don't bother with it so phones never get any updates after 1 year.

Maintaining custom Linux kernel fork is not possible if you want to keep it up with the upstream changes.

[cycloptic]

>if you want to keep it up with the upstream changes.

I don't understand what you mean here. It's my interpretation that keeping up with upstream is what was meant by answering to the community. It seems that the GP post was not concerned with this or with following the footsteps of Android. It certainly seems within Microsoft's means to deploy a custom kernel on Azure and then only periodically merge with upstream (I believe they are already doing this anyway).

[for_xyz]

Yes, I agree. What I meant was for mobile phone manufacturers who don't upstream their code portions and abandon it after a while due increased costs of maintaining the multiple versions. In other words... old hardware only works on older kernel release and new hardware only works on new kernel release.

It'd be much better if they upstreamed the changes instead of fragmenting the entire ecosystem with custom forks.