diff for duplicates of <20190509092514.GA18598@lst.de> diff --git a/a/1.txt b/N1/1.txt index 30b8489..8a0b8d5 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Thu, May 09, 2019@11:19:37AM +0200, Rafael J. Wysocki wrote: +On Thu, May 09, 2019 at 11:19:37AM +0200, Rafael J. Wysocki wrote: > Right, the choice of the target system state has already been made > when their callbacks get invoked (and it has been made by user space, > not by the platform). diff --git a/a/content_digest b/N1/content_digest index 2b6f757..d976448 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,12 +8,24 @@ "ref\0064701C3-2BD4-4D93-891D-B7FBB5040FC4@canonical.com\0" "ref\020190509065223.GA15984@lst.de\0" "ref\0CAJZ5v0h51nMCte4yL76nMWaYrrXDPrOK=CeUpc50=r2Pp_icPw@mail.gmail.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 11:25:14 +0200\0" + "To\0Rafael J. Wysocki <rafael@kernel.org>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Kai-Heng Feng <kai.heng.feng@canonical.com> + Rafael Wysocki <rafael.j.wysocki@intel.com> + Mario Limonciello <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@11:19:37AM +0200, Rafael J. Wysocki wrote:\n" + "On Thu, May 09, 2019 at 11:19:37AM +0200, Rafael J. Wysocki wrote:\n" "> Right, the choice of the target system state has already been made\n" "> when their callbacks get invoked (and it has been made by user space,\n" "> not by the platform).\n" @@ -36,4 +48,4 @@ "How do you think we best make that distinction? Are the pm_ops\n" enough if we don't use the simple version? -fc70cb3f9384d0dc57ee17b61ce3e8f75f6d5fe7cb6d31d92616b9ae86a647e8 +3356dcc88b65a9a17dec0ba81451d351c3b45a2c3f53ddfb8832dacd7e9ff1e4
diff --git a/a/1.txt b/N2/1.txt index 30b8489..f4af841 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,9 +1,9 @@ -On Thu, May 09, 2019@11:19:37AM +0200, Rafael J. Wysocki wrote: +On Thu, May 09, 2019 at 11:19:37AM +0200, Rafael J. Wysocki wrote: > Right, the choice of the target system state has already been made > when their callbacks get invoked (and it has been made by user space, > not by the platform). ->From a previous discussion I remember the main problem here is that +From a previous discussion I remember the main problem here is that a lot of consumer NVMe use more power when put into D3hot than just letting the device itself manage the power state transitions themselves. Based on this patch there also might be some other device that want diff --git a/a/content_digest b/N2/content_digest index 2b6f757..d41814d 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -8,17 +8,29 @@ "ref\0064701C3-2BD4-4D93-891D-B7FBB5040FC4@canonical.com\0" "ref\020190509065223.GA15984@lst.de\0" "ref\0CAJZ5v0h51nMCte4yL76nMWaYrrXDPrOK=CeUpc50=r2Pp_icPw@mail.gmail.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 11:25:14 +0200\0" + "To\0Rafael J. Wysocki <rafael@kernel.org>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Kai-Heng Feng <kai.heng.feng@canonical.com> + Rafael Wysocki <rafael.j.wysocki@intel.com> + Mario Limonciello <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@11:19:37AM +0200, Rafael J. Wysocki wrote:\n" + "On Thu, May 09, 2019 at 11:19:37AM +0200, Rafael J. Wysocki wrote:\n" "> Right, the choice of the target system state has already been made\n" "> when their callbacks get invoked (and it has been made by user space,\n" "> not by the platform).\n" "\n" - ">From a previous discussion I remember the main problem here is that\n" + "From a previous discussion I remember the main problem here is that\n" "a lot of consumer NVMe use more power when put into D3hot than just\n" "letting the device itself manage the power state transitions themselves.\n" "Based on this patch there also might be some other device that want\n" @@ -36,4 +48,4 @@ "How do you think we best make that distinction? Are the pm_ops\n" enough if we don't use the simple version? -fc70cb3f9384d0dc57ee17b61ce3e8f75f6d5fe7cb6d31d92616b9ae86a647e8 +793ebe5966cd47e664ee0f45162f529ebaa2fbc3668ab5475cf966ef0ec6a7e9
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.