On Fri, 3 Oct 2008 06:07:23 -0700, "Andrew Morton" <akpm@linux-foundation.org> said:
quoted text
> On Fri, 3 Oct 2008 21:44:14 +1000 Bron Gondwana <brong@fastmail.fm>
> wrote:
> > Is there a standard way to tell backporters "you really need to add this
> > patch for your users' sanity"?
> 
> Yes, there is.  We backport the patch into earlier kernel releases and
> that action _should_ wake the distros up to take a look at the fix.
> 
> This particular fix (42a886af728c089df8da1b0017b0e7e6c81b5335) was
> included in 2.6.26 and also is present in 2.6.25.17, but not 2.6.25. 
> So we did backport it into 2.6.25.x.  Maybe distros were slow or errant
> in picking up the patch.

It went into 2.6.25.8, which was the stable line at the time.  It
didn't get backported to 2.6.24.  Ubuntu's stable line is called
2.6.24-19.41, and I'm guessing they just didn't realise it was
a fix that actually needs to be applied to everything back to at
least 2.6.23.

I'll go try launchpad again and see if it's unbroken enough to
accept my bug report.

Bron ( really not wanting to keep fielding Cyrus questions on this
       for the 4 1/2 years support remaining on that LTS distro! )
-- 
  Bron Gondwana
  brong@fastmail.fm

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/