Linux Power Management development
 help / color / mirror / Atom feed
diff for duplicates of <20190509092514.GA18598@lst.de>

diff --git a/a/1.txt b/N1/1.txt
index 8a0b8d5..f4af841 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -3,7 +3,7 @@ On Thu, May 09, 2019 at 11:19:37AM +0200, Rafael J. Wysocki wrote:
 > 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/N1/content_digest
index d976448..d41814d 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -30,7 +30,7 @@
  "> 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"
@@ -48,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?
 
-3356dcc88b65a9a17dec0ba81451d351c3b45a2c3f53ddfb8832dacd7e9ff1e4
+793ebe5966cd47e664ee0f45162f529ebaa2fbc3668ab5475cf966ef0ec6a7e9

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox