diff for duplicates of <20190509065223.GA15984@lst.de> diff --git a/a/1.txt b/N1/1.txt index 277e219..85a8a1c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Thu, May 09, 2019@02:48:59PM +0800, Kai-Heng Feng wrote: +On Thu, May 09, 2019 at 02:48:59PM +0800, Kai-Heng Feng wrote: > Not really, for hibernation pm_suspend_via_s2idle() evaluates to false so > the old code path will be taken. > @@ -10,7 +10,7 @@ On Thu, May 09, 2019@02:48:59PM +0800, Kai-Heng Feng wrote: > Rafael, what do you think about this? > Including this patch, there are five drivers that use > pm_suspend_via_{firmware,s2idle}() to differentiate between S2I and S3. -> So I think maybe it?s time to introduce a new suspend callback for S2I? +> So I think maybe it’s time to introduce a new suspend callback for S2I? We also really need something like that to avoid the PCI_DEV_FLAGS_NO_D3 abuse - that flag is a quirk statically set on a device at probe time @@ -22,7 +22,7 @@ to prevent any entering of D3 state. >> quoted in the original document supports. > > If Modern Standby or Connected Standby is not supported by servers, I -> don?t think the design documents mean much here. +> don’t think the design documents mean much here. > We probably should check if the platform firmware really supports S2I > instead. diff --git a/a/content_digest b/N1/content_digest index 42629b0..879a006 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,12 +6,23 @@ "ref\0b43f2c0078f245398101fa9a40cfc2dc@AUSX13MPC105.AMER.DELL.COM\0" "ref\020190509061237.GA15229@lst.de\0" "ref\0064701C3-2BD4-4D93-891D-B7FBB5040FC4@canonical.com\0" - "From\0hch@lst.de (Christoph Hellwig)\0" - "Subject\0[PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle\0" + "From\0Christoph Hellwig <hch@lst.de>\0" + "Subject\0Re: [PATCH] nvme-pci: Use non-operational power state instead of D3 on Suspend-to-Idle\0" "Date\0Thu, 9 May 2019 08:52:23 +0200\0" + "To\0Kai-Heng Feng <kai.heng.feng@canonical.com>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + rafael.j.wysocki@intel.com + Mario.Limonciello@dell.com + Keith Busch <kbusch@kernel.org> + Keith Busch <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@02:48:59PM +0800, Kai-Heng Feng wrote:\n" + "On Thu, May 09, 2019 at 02:48:59PM +0800, Kai-Heng Feng wrote:\n" "> Not really, for hibernation pm_suspend_via_s2idle() evaluates to false so \n" "> the old code path will be taken.\n" ">\n" @@ -23,7 +34,7 @@ "> Rafael, what do you think about this?\n" "> Including this patch, there are five drivers that use \n" "> pm_suspend_via_{firmware,s2idle}() to differentiate between S2I and S3.\n" - "> So I think maybe it?s time to introduce a new suspend callback for S2I?\n" + "> So I think maybe it\342\200\231s time to introduce a new suspend callback for S2I?\n" "\n" "We also really need something like that to avoid the PCI_DEV_FLAGS_NO_D3\n" "abuse - that flag is a quirk statically set on a device at probe time\n" @@ -35,7 +46,7 @@ ">> quoted in the original document supports.\n" ">\n" "> If Modern Standby or Connected Standby is not supported by servers, I \n" - "> don?t think the design documents mean much here.\n" + "> don\342\200\231t think the design documents mean much here.\n" "> We probably should check if the platform firmware really supports S2I \n" "> instead.\n" "\n" @@ -44,4 +55,4 @@ "like nvme can just implement the behavior, but are the absolute wrong\n" place to make decisions on what kinds of suspend to enter. -2ab164f7d1211c8a038d024ff451bdc870438df3e09e84d6bc5d76936b00a416 +9d6009459c6bf9770a96b46eb52b4e4f1cfed67cc3992f23462a7fa7a18285e3
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.