diff for duplicates of <20190801202251.GD15795@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index c673002..a2c96b5 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,12 +1,12 @@ -On Thu, Aug 01, 2019@02:05:54AM -0700, Kai-Heng Feng wrote: ->@06:33, Rafael J. Wysocki <rafael@kernel.org> wrote: -> > On Thu, Aug 1, 2019@12:22 AM Keith Busch <kbusch@kernel.org> wrote: +On Thu, Aug 01, 2019 at 02:05:54AM -0700, Kai-Heng Feng wrote: +> at 06:33, Rafael J. Wysocki <rafael@kernel.org> wrote: +> > On Thu, Aug 1, 2019 at 12:22 AM Keith Busch <kbusch@kernel.org> wrote: > > > >> In which case we do need to reintroduce the HMB handling. > > > > Right. > -> The patch alone doesn?t break HMB Toshiba NVMe I tested. But I think it?s +> The patch alone doesn’t break HMB Toshiba NVMe I tested. But I think it’s > still safer to do proper HMB handling. Spec requires host request controller release HMB for D3cold. I suspect diff --git a/a/content_digest b/N1/content_digest index 68b2339..d4f1f89 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,23 +8,35 @@ "ref\020190731221956.GB15795@localhost.localdomain\0" "ref\0CAJZ5v0hxYGBXau39sb80MQ8jbZZCzH0JU2DYZvn9JOtYT2+30g@mail.gmail.com\0" "ref\070D536BE-8DC7-4CA2-84A9-AFB067BA520E@canonical.com\0" - "From\0kbusch@kernel.org (Keith Busch)\0" - "Subject\0[Regression] Commit \"nvme/pci: Use host managed power state for suspend\" has problems\0" + "From\0Keith Busch <kbusch@kernel.org>\0" + "Subject\0Re: [Regression] Commit \"nvme/pci: Use host managed power state for suspend\" has problems\0" "Date\0Thu, 1 Aug 2019 14:22:51 -0600\0" + "To\0Kai-Heng Feng <kai.heng.feng@canonical.com>\0" + "Cc\0Rafael J. Wysocki <rafael@kernel.org>" + Mario Limonciello <Mario.Limonciello@dell.com> + Rafael J. Wysocki <rjw@rjwysocki.net> + Busch + Keith <keith.busch@intel.com> + Christoph Hellwig <hch@lst.de> + Sagi Grimberg <sagi@grimberg.me> + linux-nvme <linux-nvme@lists.infradead.org> + Linux PM <linux-pm@vger.kernel.org> + Linux Kernel Mailing List <linux-kernel@vger.kernel.org> + " Rajat Jain <rajatja@google.com>\0" "\00:1\0" "b\0" - "On Thu, Aug 01, 2019@02:05:54AM -0700, Kai-Heng Feng wrote:\n" - ">@06:33, Rafael J. Wysocki <rafael@kernel.org> wrote:\n" - "> > On Thu, Aug 1, 2019@12:22 AM Keith Busch <kbusch@kernel.org> wrote:\n" + "On Thu, Aug 01, 2019 at 02:05:54AM -0700, Kai-Heng Feng wrote:\n" + "> at 06:33, Rafael J. Wysocki <rafael@kernel.org> wrote:\n" + "> > On Thu, Aug 1, 2019 at 12:22 AM Keith Busch <kbusch@kernel.org> wrote:\n" "> >\n" "> >> In which case we do need to reintroduce the HMB handling.\n" "> >\n" "> > Right.\n" "> \n" - "> The patch alone doesn?t break HMB Toshiba NVMe I tested. But I think it?s \n" + "> The patch alone doesn\342\200\231t break HMB Toshiba NVMe I tested. But I think it\342\200\231s \n" "> still safer to do proper HMB handling.\n" "\n" "Spec requires host request controller release HMB for D3cold. I suspect\n" you're only getting to D3hot. -d66d56802444d1a71410ccb15424dcd87b23ecc527bd9a2550a80d615a9dbe7b +70a900d9df13ff3dc5a99981704c7ce384feb7e4516b488691b2d5a51b914e14
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.