linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Matthew Garrett <mjg@redhat.com>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	stable@kernel.org
Subject: Re: [PATCH] Ignore pre-1.1 ASPM quirking when ASPM is disabled
Date: Thu, 8 Mar 2012 07:44:17 -0800	[thread overview]
Message-ID: <20120308154417.GA5907@kroah.com> (raw)
In-Reply-To: <20120307202553.50b6c91c@jbarnes-x220>

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@kroah.com> 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@redhat.com>
> > > Cc: stable@kernel.org
> > 
> > That's <stable@vger.kernel.org> 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

      reply	other threads:[~2012-03-08 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 18:41 [PATCH] Ignore pre-1.1 ASPM quirking when ASPM is disabled Matthew Garrett
2012-03-07  5:48 ` Greg KH
2012-03-08  4:25   ` Jesse Barnes
2012-03-08 15:44     ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120308154417.GA5907@kroah.com \
    --to=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=stable@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).