From: Alex Chiang <achiang@canonical.com>
To: Greg KH <greg@kroah.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Matthew Garrett <mjg@redhat.com>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
rjw@sisk.pl, stable@kernel.org
Subject: Re: [stable] [PATCH] pci: Ensure we re-enable devices on resume
Date: Sat, 24 Apr 2010 22:21:49 -0600 [thread overview]
Message-ID: <20100425042149.GA3010@canonical.com> (raw)
In-Reply-To: <20100423000819.GA6022@kroah.com>
* Greg KH <greg@kroah.com>:
> On Thu, Apr 22, 2010 at 05:46:53PM -0600, Alex Chiang wrote:
> > * Jesse Barnes <jbarnes@virtuousgeek.org>:
> > > Matthew Garrett <mjg@redhat.com> wrote:
> > >
> > > > If the firmware puts a device back into D0 state at
> > > > resume time, we'll update its state in resume_noirq and
> > > > thus skip the platform resume code. Calling that code
> > > > twice should be safe and we ought to avoid getting to
> > > > that point anyway, so remove the check and also allow the
> > > > platform pci code to be called for D0.
> > > >
> > > > Fixes USB not being powered after resume on recent Lenovo
> > > > machines.
> > > >
> > >
> > > Applied to for-linus, thanks.
> >
> > Stable, can you please pick this up too?
>
> When it goes into Linus's tree, yes. Care to let me know what
> the git commit id of it is when that happens?
commit cc2893b6af5265baa1d68b17b136cffca9e40cfa
Thanks!
/ac
next prev parent reply other threads:[~2010-04-25 4:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:30 [PATCH] pci: Ensure we re-enable devices on resume Matthew Garrett
2010-04-22 18:14 ` Rafael J. Wysocki
2010-04-22 19:43 ` Alex Chiang
2010-04-22 23:17 ` Jesse Barnes
2010-04-22 23:46 ` Alex Chiang
2010-04-23 0:08 ` [stable] " Greg KH
2010-04-25 4:21 ` Alex Chiang [this message]
2010-05-07 20:43 ` Greg KH
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=20100425042149.GA3010@canonical.com \
--to=achiang@canonical.com \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
--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).