LWN: Comments on "A long-term kernel support update" https://lwn.net/Articles/474871/ This is a special feed containing comments posted to the individual LWN article titled "A long-term kernel support update". en-us Tue, 21 Oct 2025 19:12:32 +0000 Tue, 21 Oct 2025 19:12:32 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net A long-term kernel support update https://lwn.net/Articles/474946/ https://lwn.net/Articles/474946/ oseemann <div class="FormattedComment"> You are right. I meant that I'd be happy to see 3.2 (or later) as a longterm release, instead of 3.0, because of the writeback changes.<br> </div> Wed, 11 Jan 2012 09:16:55 +0000 A long-term kernel support update https://lwn.net/Articles/474938/ https://lwn.net/Articles/474938/ jrn <div class="FormattedComment"> $ git log 7cf801cfc077 ^origin/master<br> $<br> <p> Merged today at 10:55 pacific time, apparently, if "git log --ancestry-path 7cf801cfc077..origin/master" is not tricking me.<br> </div> Wed, 11 Jan 2012 01:03:30 +0000 A long-term kernel support update https://lwn.net/Articles/474928/ https://lwn.net/Articles/474928/ pkern <div class="FormattedComment"> Then I have to take that back. Kudos to Seth! Any idea when this will land in<br> mainline, if it didn't already? I guess the author would need to send an<br> explicit merge requests to take something from -next?<br> <p> </div> Tue, 10 Jan 2012 23:09:11 +0000 A long-term kernel support update https://lwn.net/Articles/474914/ https://lwn.net/Articles/474914/ corbet The writeback changes are big and intrusive, though; they are just the sort of thing that is <i>not</i> supposed to go into stable updates. Tue, 10 Jan 2012 22:11:57 +0000 A long-term kernel support update https://lwn.net/Articles/474913/ https://lwn.net/Articles/474913/ oseemann <div class="FormattedComment"> I'd be happy to see the next longtime kernel include the recent writeback changes, which came in with 3.2.<br> </div> Tue, 10 Jan 2012 22:08:38 +0000 A long-term kernel support update https://lwn.net/Articles/474909/ https://lwn.net/Articles/474909/ jrn <div class="FormattedComment"> linux-next seems to include support for recent ALPS touchpads (commit 25bded7cd60f, "Input: ALPS - add support for protocol versions 3 and 4"). Does it not work? Any links for people who missed the fuss?<br> </div> Tue, 10 Jan 2012 22:01:58 +0000 A long-term kernel support update https://lwn.net/Articles/474898/ https://lwn.net/Articles/474898/ pkern <div class="FormattedComment"> They should've tried harder to push Dell and ALPS to provide a sane driver. As far as I know the current patchset was rejected upstream because it's only doing magical undocumented initialization and then falling back to a dumber protocol (i.e. IMPS/2) than you'd normally talk with a touchpad. In the end, if customers actually had a choice, they'd avoid the Dell laptops for exactly that reason (and if you use the touchpad, it is dazed and confused even with the patch once in a while).<br> </div> Tue, 10 Jan 2012 20:42:21 +0000 A long-term kernel support update https://lwn.net/Articles/474883/ https://lwn.net/Articles/474883/ iabervon <div class="FormattedComment"> I imagine they'd find it most straightforward to follow the usual long-term support procedure to generate a vanilla 2.6.32.x, and they add their own patches to that. If you don't follow the standard practice, there's no benefit to officially adopting the series.<br> <p> </div> Tue, 10 Jan 2012 17:02:03 +0000 A long-term kernel support update https://lwn.net/Articles/474879/ https://lwn.net/Articles/474879/ mpagano <div class="FormattedComment"> I hope Ubuntu does upstream their patchset but from their history and current actions (see ALPS Dell patchset), I have doubts.<br> </div> Tue, 10 Jan 2012 16:38:37 +0000