diff for duplicates of <1495157575349.14067@Dell.com> diff --git a/a/content_digest b/N1/content_digest index f08e59e..84f7396 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,8 +1,16 @@ "ref\0ddc5be5d81966effaf73e3cee54330c351bc8169.1494561654.git.luto@kernel.org\0" "ref\0CALCETrUYutdtp5U7oYwf7-eNuB0MrwoC18mG5-S8iOP4ZEVDuA@mail.gmail.com\0" - "From\0Mario.Limonciello@dell.com (Mario.Limonciello@dell.com)\0" - "Subject\0[PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe\0" + "From\0<Mario.Limonciello@dell.com>\0" + "Subject\0Re: [PATCH] nvme: Change our APST table to be no more aggressive than Intel RSTe\0" "Date\0Fri, 19 May 2017 01:32:55 +0000\0" + "To\0<luto@kernel.org>\0" + "Cc\0<axboe@kernel.dk>" + <linux-kernel@vger.kernel.org> + <kai.heng.feng@canonical.com> + <linux-nvme@lists.infradead.org> + <hch@lst.de> + <sagi@grimberg.me> + " <keith.busch@intel.com>\0" "\00:1\0" "b\0" "> I pondered this a bit, and I want to NAK my own patch. This patch\n" @@ -39,4 +47,4 @@ "\n" I would second this and love if Intel could speak up here on what direction they recommend to bring the NVME driver for APST. -3d69c78d2296320e15d997b71e4ad62be46fb3aa404df584f893fedd3830b9d9 +0401e614e1ec0c45c46be82d3f7d5417e1999f94e10d23c0ad8b2f708cef87f1
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.