| |||||||||||||
Long-term support initiative 3.4 kernel releasedLong-term support initiative 3.4 kernel releasedPosted Jan 22, 2013 16:25 UTC (Tue) by arjan (subscriber, #36785)Parent article: Long-term support initiative 3.4 kernel released
hmmmm stable kernels adding kernel ABI/API's (AF_DBUS) that are not even in upstream yet? That sounds like a disaster waiting to happen...
(Log in to post comments)
Long-term support initiative 3.4 kernel released Posted Jan 22, 2013 17:13 UTC (Tue) by engla (guest, #47454) [Link]
Maybe it's natural if a single central person blocks progress on a feature.
Long-term support initiative 3.4 kernel released Posted Jan 22, 2013 17:17 UTC (Tue) by arjan (subscriber, #36785) [Link]
NO it is absolutely NOT natural.
Stable kernels should not add non-upstream ABI/APIs
bypassing the upstream process is not a valid option.
this is to the level where this guy should be stripped from it's kernel.org official status
Long-term support initiative 3.4 kernel released Posted Jan 22, 2013 17:25 UTC (Tue) by BenHutchings (subscriber, #37955) [Link]
LTSI is hosted by the Linux Foundation, not kernel.org.
Long-term support initiative 3.4 kernel released Posted Jan 22, 2013 18:33 UTC (Tue) by Jonno (subscriber, #49613) [Link]
Remember, this is essentially CEWG's (Consumer Electronics Work Group) response to the Android kernel, intended for device manufacturers and other embedded developers to do their SoC work on when targeting non-Android Linux.
As such, I'm rather surprised at the *low* amount of non-upstream patches included...
Also, this isn't really something new, they have been doing this as a git branch of first 3.0 and later 3.4 since August 2011, they have just never bothered doing releases before (as everyone using it would be doing their own development in git on top of it anyway).
Long-term support initiative 3.4 kernel released Posted Jan 22, 2013 18:57 UTC (Tue) by arjan (subscriber, #36785) [Link]
I don't mind non-upstream patches nearly as much as non-stream API/ABIs.
The latter means userspace software gets written assuming "number X means Y"... which won't be the case in upstream, when number X gets reused.. say for AF_FOO instead of AF_DBUS. And then you get an application compatibility nightmare.
Long-term support initiative 3.4 kernel released Posted Jan 22, 2013 19:31 UTC (Tue) by Cyberax (✭ supporter ✭, #52523) [Link]
Well, reserve a number for it, then. Or be prepared to repeat the whole Android saga.
|
|||||||||||||