From: Lukas Wunner <lukas@wunner.de>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] PCI: pciehp: Fix hotplug on Catlow Lake with unreliable PME status
Date: Mon, 16 Nov 2026 12:30:17 +0100 [thread overview]
Message-ID: <avrpSRJ0ONIYZHI8@wunner.de> (raw)
In-Reply-To: <c7a3ef34-27f0-4b0b-8eab-db0fff15588d@linux.intel.com>
On Wed, Oct 07, 2026 at 12:55:58PM -0700, Kuppuswamy Sathyanarayanan wrote:
> So both drivers are possible places for
> the fix, and I would like your and Bjorn's preference before sending v5.
>
> 1. pciehp route (v4)
[...]
> 2. PME route
I am very sorry for not responding earlier. I just wanted to say,
I think you made the right call to pick the PME route in v5.
Thanks,
Lukas
prev parent reply other threads:[~2026-11-16 11:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 22:08 Kuppuswamy Sathyanarayanan
2026-03-23 12:53 ` Lukas Wunner
2026-03-23 23:24 ` Bjorn Helgaas
2026-03-24 21:45 ` Kuppuswamy Sathyanarayanan
2026-03-24 23:46 ` Bjorn Helgaas
2026-03-25 5:56 ` Lukas Wunner
2026-03-25 23:21 ` Bjorn Helgaas
2026-03-25 6:11 ` Mika Westerberg
2026-03-25 21:12 ` Kuppuswamy Sathyanarayanan
2026-03-26 6:12 ` Mika Westerberg
2026-03-26 21:23 ` Kuppuswamy Sathyanarayanan
2026-03-27 11:16 ` Mika Westerberg
2026-04-03 19:37 ` Kuppuswamy Sathyanarayanan
2026-04-07 7:08 ` Mika Westerberg
2026-09-11 17:01 ` Kuppuswamy Sathyanarayanan
2026-09-24 18:46 ` Kuppuswamy Sathyanarayanan
2026-09-25 5:19 ` Mika Westerberg
2026-09-25 17:38 ` Kuppuswamy Sathyanarayanan
2026-09-25 18:35 ` Lukas Wunner
2026-09-29 17:42 ` Kuppuswamy Sathyanarayanan
2026-10-07 19:55 ` Kuppuswamy Sathyanarayanan
2026-10-20 17:37 ` Kuppuswamy Sathyanarayanan
2026-11-16 11:30 ` Lukas Wunner [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=avrpSRJ0ONIYZHI8@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@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
all inboxes | Powered by JetHome®