diff for duplicates of <20180723224507.GA11656@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index 662b6e2..0d9875f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Mon, Jul 23, 2018@04:24:31PM -0600, Alex Williamson wrote: +On Mon, Jul 23, 2018 at 04:24:31PM -0600, Alex Williamson wrote: > Take advantage of NVMe devices using a standard interface to quiesce > the controller prior to reset, including device specific delays before > and after that reset. This resolves several NVMe device assignment @@ -17,3 +17,8 @@ On Mon, Jul 23, 2018@04:24:31PM -0600, Alex Williamson wrote: > to all devices with matching class code. Shouldn't this go in the nvme driver's reset_prepare/reset_done callbacks? + +_______________________________________________ +Linux-nvme mailing list +Linux-nvme@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-nvme diff --git a/a/content_digest b/N1/content_digest index e56471d..80dc557 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,11 +1,15 @@ "ref\020180723221533.4371.90064.stgit@gimli.home\0" "ref\020180723222431.4371.25962.stgit@gimli.home\0" - "From\0keith.busch@intel.com (Keith Busch)\0" - "Subject\0[PATCH 2/2] PCI: NVMe device specific reset quirk\0" + "From\0Keith Busch <keith.busch@intel.com>\0" + "Subject\0Re: [PATCH 2/2] PCI: NVMe device specific reset quirk\0" "Date\0Mon, 23 Jul 2018 16:45:08 -0600\0" + "To\0Alex Williamson <alex.williamson@redhat.com>\0" + "Cc\0linux-pci@vger.kernel.org" + linux-kernel@vger.kernel.org + " linux-nvme@lists.infradead.org\0" "\00:1\0" "b\0" - "On Mon, Jul 23, 2018@04:24:31PM -0600, Alex Williamson wrote:\n" + "On Mon, Jul 23, 2018 at 04:24:31PM -0600, Alex Williamson wrote:\n" "> Take advantage of NVMe devices using a standard interface to quiesce\n" "> the controller prior to reset, including device specific delays before\n" "> and after that reset. This resolves several NVMe device assignment\n" @@ -23,6 +27,11 @@ "> specification also requires PCIe FLR support, we can apply this quirk\n" "> to all devices with matching class code.\n" "\n" - Shouldn't this go in the nvme driver's reset_prepare/reset_done callbacks? + "Shouldn't this go in the nvme driver's reset_prepare/reset_done callbacks?\n" + "\n" + "_______________________________________________\n" + "Linux-nvme mailing list\n" + "Linux-nvme@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-nvme -f1bbc8d7f74bd54fec460623dadbabe7de10bbe42c70300c745e55912e1f906b +41c79f2cbf154b38e25562ae0f9dbfe00397713339c7901493cc10b8f4f9c6bd
diff --git a/a/1.txt b/N2/1.txt index 662b6e2..59a1b24 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,4 +1,4 @@ -On Mon, Jul 23, 2018@04:24:31PM -0600, Alex Williamson wrote: +On Mon, Jul 23, 2018 at 04:24:31PM -0600, Alex Williamson wrote: > Take advantage of NVMe devices using a standard interface to quiesce > the controller prior to reset, including device specific delays before > and after that reset. This resolves several NVMe device assignment diff --git a/a/content_digest b/N2/content_digest index e56471d..6517996 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -1,11 +1,15 @@ "ref\020180723221533.4371.90064.stgit@gimli.home\0" "ref\020180723222431.4371.25962.stgit@gimli.home\0" - "From\0keith.busch@intel.com (Keith Busch)\0" - "Subject\0[PATCH 2/2] PCI: NVMe device specific reset quirk\0" + "From\0Keith Busch <keith.busch@intel.com>\0" + "Subject\0Re: [PATCH 2/2] PCI: NVMe device specific reset quirk\0" "Date\0Mon, 23 Jul 2018 16:45:08 -0600\0" + "To\0Alex Williamson <alex.williamson@redhat.com>\0" + "Cc\0linux-pci@vger.kernel.org" + linux-kernel@vger.kernel.org + " linux-nvme@lists.infradead.org\0" "\00:1\0" "b\0" - "On Mon, Jul 23, 2018@04:24:31PM -0600, Alex Williamson wrote:\n" + "On Mon, Jul 23, 2018 at 04:24:31PM -0600, Alex Williamson wrote:\n" "> Take advantage of NVMe devices using a standard interface to quiesce\n" "> the controller prior to reset, including device specific delays before\n" "> and after that reset. This resolves several NVMe device assignment\n" @@ -25,4 +29,4 @@ "\n" Shouldn't this go in the nvme driver's reset_prepare/reset_done callbacks? -f1bbc8d7f74bd54fec460623dadbabe7de10bbe42c70300c745e55912e1f906b +3cb1e41650bfd01e02c61740a260d49b52d8323b57e1a426b85cdf4ea4650eb4
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.