diff for duplicates of <20190509162038.GC9548@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index 0343969..e5f0470 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,11 +1,11 @@ -On Thu, May 09, 2019@03:28:32AM -0700, Kai-Heng Feng wrote: ->@17:56, Christoph Hellwig <hch@lst.de> wrote: +On Thu, May 09, 2019 at 03:28:32AM -0700, Kai-Heng Feng wrote: +> at 17:56, Christoph Hellwig <hch@lst.de> wrote: > > The we have the sequence in your patch. This seems to be related to > > some of the MS wording, but I'm not sure what for example tearing down > > the queues buys us. Can you explain a bit more where those bits > > make a difference? > -> Based on my testing if queues (IRQ) are not disabled, NVMe controller won?t +> Based on my testing if queues (IRQ) are not disabled, NVMe controller won’t > be quiesced. > Symptoms can be high power drain or system freeze. > diff --git a/a/content_digest b/N1/content_digest index 0258075..9503d78 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,19 +8,32 @@ "ref\0A4DD2E9F-054E-4D4B-9F77-D69040EBE120@canonical.com\0" "ref\020190509095601.GA19041@lst.de\0" "ref\0225CF4F7-C8E1-4C66-B362-97E84596A54E@canonical.com\0" - "From\0kbusch@kernel.org (Keith Busch)\0" - "Subject\0[PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle\0" + "From\0Keith Busch <kbusch@kernel.org>\0" + "Subject\0Re: [PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle\0" "Date\0Thu, 9 May 2019 10:20:38 -0600\0" + "To\0Kai-Heng Feng <kai.heng.feng@canonical.com>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Rafael J. Wysocki <rafael@kernel.org> + Wysocki + Rafael J <rafael.j.wysocki@intel.com> + Mario Limonciello <Mario.Limonciello@dell.com> + Busch + Keith <keith.busch@intel.com> + Jens Axboe <axboe@fb.com> + Sagi Grimberg <sagi@grimberg.me> + linux-nvme <linux-nvme@lists.infradead.org> + Linux PM <linux-pm@vger.kernel.org> + " LKML <linux-kernel@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Thu, May 09, 2019@03:28:32AM -0700, Kai-Heng Feng wrote:\n" - ">@17:56, Christoph Hellwig <hch@lst.de> wrote:\n" + "On Thu, May 09, 2019 at 03:28:32AM -0700, Kai-Heng Feng wrote:\n" + "> at 17:56, Christoph Hellwig <hch@lst.de> wrote:\n" "> > The we have the sequence in your patch. This seems to be related to\n" "> > some of the MS wording, but I'm not sure what for example tearing down\n" "> > the queues buys us. Can you explain a bit more where those bits\n" "> > make a difference?\n" "> \n" - "> Based on my testing if queues (IRQ) are not disabled, NVMe controller won?t \n" + "> Based on my testing if queues (IRQ) are not disabled, NVMe controller won\342\200\231t \n" "> be quiesced.\n" "> Symptoms can be high power drain or system freeze.\n" "> \n" @@ -36,4 +49,4 @@ "We shouldn't have to do anything to exit the state as the spec requires\n" devices autonomously return to operational when an IO doorbell is written. -1b53d0d371ac60f8f43412590040478774913443083ae4fc6e2bed4af846eb2c +6ef8e38e3c973551577aa22de0a4464a63253e2cc7252e97814f27a2a68cc195
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.