3 ms·
> All that horrible forked kernel stuff is the realm of companies with closed development teams who don't care and just want a product out the door. Or people
by lmm 6y ago
> All that horrible forked kernel stuff is the realm of companies with closed development teams who don't care and just want a product out the door.
Or people who gave upstreaming an honest try but got fed up. It's not the easiest project to contribute to.
- marcan_42 6y agoYou do need to know what you're doing, meet quality standards, and do things in a way that fits existing architecture (unless you have a really good reason to revamp something). It's not beginner-friendly for sure, but I can tell you the vast majority of non-upstreamed vendor code is not upstreamed because it's terrible (which is also bad for users: things like blatant security problems are much more common in forks than upstream).
- krageon 6y agoIf you can't be bothered to learn how to write linux kernel patches properly you shouldn't be making them at all, in a forked kernel or otherwise.