From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, Greg KH <greg@kroah.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
len.brown@intel.com, Shaohua Li <shaohua.li@intel.com>
Subject: Re: Suspend/Resume bug in PCI layer wrt quirks
Date: Fri, 16 May 2008 22:16:30 +0200 [thread overview]
Message-ID: <200805162216.31463.rjw@sisk.pl> (raw)
In-Reply-To: <200805161051.49919.jbarnes@virtuousgeek.org>
On Friday, 16 of May 2008, Jesse Barnes wrote:
> On Thursday, May 15, 2008 12:51 pm Rafael J. Wysocki wrote:
> > Some quirks should be called with interrupt disabled, we can't directly
> > call them in .resume_early. Also the patch introduces
> > pci_fixup_resume_early and pci_fixup_suspend, which matches current
> > device core callbacks (.suspend/.resume_early).
> >
> > TBD: Somebody knows why we need quirk resume should double check if a
> > quirk should be called in resume or resume_early. I changed some per my
> > understanding, but can't make sure I fixed all.
> >
> > Signed-off-by: Shaohua Li <shaohua.li@intel.com>
>
> I applied this one to linux-next, it should fix some of the problems people
> have been seeing at least...
Well, that will collide with
pm-new-suspend-and-hibernation-callbacks-for-pci-bus-type.patch
in the Greg's tree.
Greg, perhaps it's better if you drop it and I'll send an updated version to
Jesse? That will make his tree dependent on yours, but that will be okay,
won't it?
Thanks,
Rafael
next prev parent reply other threads:[~2008-05-16 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 14:05 Arjan van de Ven
2008-05-15 16:07 ` Jesse Barnes
2008-05-15 17:54 ` Arjan van de Ven
2008-05-15 19:51 ` Rafael J. Wysocki
2008-05-16 17:51 ` Jesse Barnes
2008-05-16 20:16 ` Rafael J. Wysocki [this message]
2008-05-16 21:37 ` Greg KH
2008-05-19 19:09 ` Jesse Barnes
2008-05-19 22:49 ` Rafael J. Wysocki
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=200805162216.31463.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
/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
all inboxes | Powered by JetHome®