From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: David Box <david.e.box@linux.intel.com>,
"Jingar, Rajvi" <rajvi.jingar@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v5 2/2] PCI/PM: Fix pci_pm_suspend_noirq() to disable PTM
Date: Mon, 23 May 2022 13:32:38 -0500 [thread overview]
Message-ID: <20220523183238.GA174199@bhelgaas> (raw)
In-Reply-To: <CAJZ5v0iHgtTpW+ox=wK68cnuG6D+KvFiOCh2UF96dxq08Z3BSA@mail.gmail.com>
On Thu, May 19, 2022 at 09:01:27PM +0200, Rafael J. Wysocki wrote:
> ...
> In the meantime, I think that it would make sense to pick up the first
> patch in this series which is a good cleanup regardless.
>
> Bjorn, could you do that, please?
As far as I know, this series has never actually made it to
linux-pci@vger.kernel.org, so I haven't seen the 1/2 patch. This
query:
https://lore.kernel.org/linux-pci/?q=f%3Arajvi.jingar
finds only a couple responses. I did mention this to Rajvi, but
haven't heard anything yet.
Bjorn
next prev parent reply other threads:[~2022-05-23 18:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220429210538.2270472-1-rajvi.jingar@intel.com>
[not found] ` <20220429210538.2270472-2-rajvi.jingar@intel.com>
2022-05-12 13:49 ` [PATCH v5 2/2] PCI/PM: Fix pci_pm_suspend_noirq() to disable PTM Rafael J. Wysocki
2022-05-12 17:42 ` Bjorn Helgaas
2022-05-12 17:52 ` Rafael J. Wysocki
2022-05-12 18:35 ` Bjorn Helgaas
2022-05-13 22:00 ` Jingar, Rajvi
2022-05-14 17:12 ` Rafael J. Wysocki
2022-05-16 20:09 ` Bjorn Helgaas
2022-05-16 20:59 ` Rafael J. Wysocki
2022-05-17 14:48 ` Bjorn Helgaas
2022-05-17 14:54 ` Rafael J. Wysocki
2022-05-17 18:05 ` David E. Box
2022-05-19 19:01 ` Rafael J. Wysocki
2022-05-23 18:32 ` Bjorn Helgaas [this message]
2022-05-23 19:02 ` 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=20220523183238.GA174199@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=david.e.box@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=rajvi.jingar@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).