From: Bjorn Helgaas <helgaas@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Rajvi Jingar <rajvi.jingar@linux.intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>,
David Box <david.e.box@linux.intel.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: [RESEND PATCH v3 1/2] PCI/PM: refactor pci_pm_suspend_noirq()
Date: Tue, 30 Aug 2022 11:20:56 -0500 [thread overview]
Message-ID: <20220830162056.GA106242@bhelgaas> (raw)
In-Reply-To: <20220830161741.GA105724@bhelgaas>
On Tue, Aug 30, 2022 at 11:17:43AM -0500, Bjorn Helgaas wrote:
> On Tue, Aug 30, 2022 at 01:44:43PM +0200, Rafael J. Wysocki wrote:
> > On Tue, Aug 30, 2022 at 12:49 PM Rajvi Jingar
> > > v1->v2: no change
> > > v2->v3: no change
>
> Why are we bumping the version numbers if there's truly no change?
Sorry, ignore this question; I see that patch 2/2 is changing.
prev parent reply other threads:[~2022-08-30 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 10:49 [RESEND PATCH v3 1/2] PCI/PM: refactor pci_pm_suspend_noirq() Rajvi Jingar
2022-08-30 10:49 ` [RESEND PATCH v3 2/2] PCI/PTM: fix to maintain pci_dev->ptm_enabled Rajvi Jingar
2022-08-30 16:25 ` Bjorn Helgaas
2022-08-30 16:58 ` Rafael J. Wysocki
2022-08-30 17:37 ` Bjorn Helgaas
2022-08-30 18:03 ` Rafael J. Wysocki
2022-08-30 19:46 ` Bjorn Helgaas
2022-08-31 17:53 ` Rafael J. Wysocki
2022-09-01 21:26 ` Bjorn Helgaas
2022-09-03 17:03 ` Rafael J. Wysocki
2022-08-30 11:44 ` [RESEND PATCH v3 1/2] PCI/PM: refactor pci_pm_suspend_noirq() Rafael J. Wysocki
2022-08-30 16:17 ` Bjorn Helgaas
2022-08-30 16:20 ` Bjorn Helgaas [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=20220830162056.GA106242@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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.