* H. Peter Anvin <hpa@xxxxxxxxx> wrote: > On 08/19/2010 12:06 PM, D. Stussy wrote: > > Has this patch been posted to the 2.6.35 kernel also, or just to 2.6.36? I don't think it's been posted to 2.6.35 where the problem it corrects was introduced. > > > > "Greg KH" <gregkh@xxxxxxx> has made a last call (tomorrow - Aug 20) for chnges for 2.6.35.3 and doesn't seem to have this. It's not in the prior two updates either..... > > It was Cc: <stable@xxxxxxxxxx>; it's up to Greg to include it or not. I think Greg generally includes all upstream commits marked with a -stable tag - except if it wont apply cleanly, in which case he mails for a backport. It of course has to fit in the regular stable release cycle, so the patches dont propagate instantaneously. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|