From: "Bjørn Mork" <bjorn@mork.no>
To: Huang Ying <ying.huang@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH 0/4] PCI/PM: PCI D3cold support fixes for 3.6-rc1
Date: Sun, 19 Aug 2012 12:35:53 +0200 [thread overview]
Message-ID: <87393jmanq.fsf@nemi.mork.no> (raw)
In-Reply-To: <1343975435-25469-1-git-send-email-ying.huang@intel.com> (Huang Ying's message of "Fri, 3 Aug 2012 14:30:31 +0800")
Huang Ying <ying.huang@intel.com> writes:
> [BUGFIX 1/4] PCI/PM: enable D3/D3cold by default for most devices
> [BUGFIX 2/4] PCI/PM: Keep parent bridge active when probing device
> [BUGFIX 3/4] PCI/PM: Fix config reg access for D3cold and bridge suspending
> [PATCH 4/4] PCI/PM: Add ABI document for sysfs file d3cold_allowed
Hello,
I am hoping these patches will appear in 3.6? They fix real problems in
3.6-rc1 for me. If it helps in any way, feel free to add
Tested-by: Bjørn Mork <bjorn@mork.no>
to the 3 bugfix patches, including version 2 of patch #3.
Bjørn
next prev parent reply other threads:[~2012-08-19 10:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 6:30 [PATCH 0/4] PCI/PM: PCI D3cold support fixes for 3.6-rc1 Huang Ying
2012-08-03 6:30 ` [BUGFIX 1/4] PCI/PM: enable D3/D3cold by default for most devices Huang Ying
2012-08-04 21:46 ` Rafael J. Wysocki
2012-08-03 6:30 ` [BUGFIX 2/4] PCI/PM: Keep parent bridge active when probing device Huang Ying
2012-08-04 21:48 ` Rafael J. Wysocki
2012-08-03 6:30 ` [BUGFIX 3/4] PCI/PM: Fix config reg access for D3cold and bridge suspending Huang Ying
2012-08-03 14:46 ` Alan Stern
2012-08-04 21:37 ` Rafael J. Wysocki
2012-08-04 21:44 ` Rafael J. Wysocki
2012-08-03 6:30 ` [PATCH 4/4] PCI/PM: Add ABI document for sysfs file d3cold_allowed Huang Ying
2012-08-19 10:35 ` Bjørn Mork [this message]
2012-08-20 1:09 ` [PATCH 0/4] PCI/PM: PCI D3cold support fixes for 3.6-rc1 huang ying
2012-08-21 23:47 ` Bjorn Helgaas
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=87393jmanq.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=ying.huang@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;
as well as URLs for NNTP newsgroup(s).