On 08/06/2016 03:56, Greg KH wrote: > On Mon, Jun 06, 2016 at 09:36:47AM +0200, Mason wrote: >> Hello, >> >> I read the kernel summit summary. >> https://lwn.net/Articles/662966/ >> >> I was wondering if the 4.4 release set a "precedent" in that the >> next few LTS releases going forward would be aimed for early Q1? > > Probably. Bummer. >> The reason I'm asking is that my company plans to release an SDK >> in Q4, and I was hoping to bundle a recent kernel. > > Nothing preventing you from always just advancing your kernel to the > latest LTS one when it comes out, right? Some customers, once they have something working, they don't want to change anything. If I release a v4.4-based SDK, and then such a customer comes along, I'll be stuck having to support v4.4 until my beard is grey. (I was told we are still expected to support several 2.6 kernels.) >> I currently provide 4.4 but most of my port was accepted in later >> versions. I was hoping I wouldn't need to backport all that code. >> >> What do the tea leaves say? > > Something in Q1, no idea what number specifically, but if all of your > code is already merged upstream, it doesn't really matter what you pick, > anything will end up working for you. The platform code got merged in 4.5 and 4.6 but I'm still missing several important (but non-essential) drivers. Thus 4.4 isn't really helpful to me, I'd have to port everything. By the way, looking at the LTS releases, it seems some (older) releases are supported longer than others (3.16, 3.12, 3.10, 3.4, 3.2). Is that because some are supported by other groups/distros? (IIUC, many Android devices run 3.4 and 3.10) https://www.kernel.org/category/releases.html Regards. -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html