On Wed, Mar 07, 2012 at 08:25:53PM -0800, Jesse Barnes wrote: > On Tue, 6 Mar 2012 21:48:59 -0800 > Greg KH <greg@xxxxxxxxx> wrote: > > > On Tue, Mar 06, 2012 at 01:41:49PM -0500, Matthew Garrett wrote: > > > Right now we won't touch ASPM state if ASPM is disabled, except in > > > the case where we find a device that appears to be too old to > > > reliably support ASPM. Right now we'll clear it in that case, which > > > is almost certainly the wrong thing to do. The easiest way around > > > this is just to disable the blacklisting when ASPM is disabled. > > > > > > Signed-off-by: Matthew Garrett <mjg@xxxxxxxxxx> > > > Cc: stable@xxxxxxxxxx > > > > That's <stable@xxxxxxxxxxxxxxx> if we want to get it right :) > > > > Anyway, Jesse, this needs to get into 3.3-final to prevent > > regressions... > > Any bz links to add to the changelog? I'll fix up the stable cc when I > commit... Not that I know of, there was an email thread about this when I released the 3.2.5 kernel that talked about the problems with it which caused this patch to be created. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
