From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Linux PCI <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: Linux ACPI <linux-acpi@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH 0/3] PCI / ACPI / PM: Fix propagation of wakeup settings to bridges
Date: Fri, 28 Jul 2017 02:34:48 +0200 [thread overview]
Message-ID: <2614123.s9HPuis7tD@aspire.rjw.lan> (raw)
In-Reply-To: <3116391.JNS1F4DjTg@aspire.rjw.lan>
On Friday, July 21, 2017 02:36:44 PM Rafael J. Wysocki wrote:
> Hi,
>
> The device wakeup code in pci-acpi.c currently has a (theoretical) problem that
> it can disable wakeup for a bridge prematurely in some obscure conditions.
>
> This is described in some more detail in the changelog of patch [3/3] and it
> has been there for quite a while, so it's nothing new, but it would be good
> to fix it at last and hence this series.
>
> Patches [1/3] and [2/3] are mostly preparatory, although the former may be
> regarded as a fix by itself and the latter is a cleanup.
Hi Bjorn,
Since all of the patches in this series have been reviewed by Mika now, please
let me know if you have any concerns regarding them from the PCI angle.
Otherwise I'm going to queue them up for 4.14 early next week.
Thanks,
Rafael
prev parent reply other threads:[~2017-07-28 0:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 12:36 [PATCH 0/3] PCI / ACPI / PM: Fix propagation of wakeup settings to bridges Rafael J. Wysocki
2017-07-21 12:38 ` [PATCH 1/3] PCI / PM: Skip bridges in pci_enable_wake() Rafael J. Wysocki
2017-07-25 12:44 ` Mika Westerberg
2017-07-31 20:53 ` Bjorn Helgaas
2017-07-31 20:59 ` Rafael J. Wysocki
2017-07-21 12:40 ` [PATCH 2/3] ACPI / PM: Split acpi_device_wakeup() Rafael J. Wysocki
2017-07-21 15:27 ` Andy Shevchenko
2017-07-21 20:49 ` Rafael J. Wysocki
2017-07-21 21:19 ` Andy Shevchenko
2017-07-21 21:16 ` Rafael J. Wysocki
2017-07-21 21:31 ` Andy Shevchenko
2017-07-21 21:25 ` Rafael J. Wysocki
2017-07-25 12:45 ` Mika Westerberg
2017-07-21 12:42 ` [PATCH 3/3] ACPI / PCI / PM: Rework acpi_pci_propagate_wakeup() Rafael J. Wysocki
2017-07-21 15:45 ` Andy Shevchenko
2017-07-21 20:44 ` Rafael J. Wysocki
2017-07-21 21:02 ` Rafael J. Wysocki
2017-07-21 21:30 ` [PATCH v2 " Rafael J. Wysocki
2017-07-21 21:43 ` Andy Shevchenko
2017-07-25 12:46 ` Mika Westerberg
2017-07-31 21:59 ` Bjorn Helgaas
2017-08-01 0:39 ` Rafael J. Wysocki
2017-08-01 0:56 ` [PATCH v3 " Rafael J. Wysocki
2017-07-28 0:34 ` Rafael J. Wysocki [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=2614123.s9HPuis7tD@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bhelgaas@google.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mika.westerberg@linux.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