diff for duplicates of <20170713162915.GA14716@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index 119feac..7cdbfb2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -26,7 +26,7 @@ On Thu, Jul 13, 2017 at 11:44:12AM -0400, Sinan Kaya wrote: > wait before issuing Configuration Requests to a Device or Function following DRS > Events or FRS Events. RN includes both the Device Readiness Status (DRS) and > Function Readiness Status (FRS) mechanisms. These mechanisms provide a direct -> indication of Configuration-Readiness (see 5 Terms and Acronyms entry for “Configuration-Ready”). +> indication of Configuration-Readiness (see 5 Terms and Acronyms entry for ?Configuration-Ready?). > > When used, DRS and FRS allow an improved behavior over the CRS mechanism, and eliminate > its associated periodic polling time of up to 1 second following a reset." diff --git a/a/content_digest b/N1/content_digest index 3e9dda1..74e4bb7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,20 +1,10 @@ "ref\01499375234-23928-1-git-send-email-okaya@codeaurora.org\0" "ref\020170713121758.GL4486@bhelgaas-glaptop.roam.corp.google.com\0" "ref\00bcc0b00-1ad3-6866-32ab-15da8ea1821e@codeaurora.org\0" - "From\0Keith Busch <keith.busch@intel.com>\0" - "Subject\0Re: [PATCH V4] PCI: handle CRS returned by device after FLR\0" + "From\0keith.busch@intel.com (Keith Busch)\0" + "Subject\0[PATCH V4] PCI: handle CRS returned by device after FLR\0" "Date\0Thu, 13 Jul 2017 12:29:16 -0400\0" - "To\0Sinan Kaya <okaya@codeaurora.org>\0" - "Cc\0Bjorn Helgaas <helgaas@kernel.org>" - linux-pci@vger.kernel.org - timur@codeaurora.org - alex.williamson@redhat.com - vikrams@codeaurora.org - Lorenzo.Pieralisi@arm.com - linux-arm-msm@vger.kernel.org - linux-kernel@vger.kernel.org - Bjorn Helgaas <bhelgaas@google.com> - " linux-arm-kernel@lists.infradead.org\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On Thu, Jul 13, 2017 at 11:44:12AM -0400, Sinan Kaya wrote:\n" @@ -45,7 +35,7 @@ "> wait before issuing Configuration Requests to a Device or Function following DRS\n" "> Events or FRS Events. RN includes both the Device Readiness Status (DRS) and\n" "> Function Readiness Status (FRS) mechanisms. These mechanisms provide a direct\n" - "> indication of Configuration-Readiness (see 5 Terms and Acronyms entry for \342\200\234Configuration-Ready\342\200\235). \n" + "> indication of Configuration-Readiness (see 5 Terms and Acronyms entry for ?Configuration-Ready?). \n" "> \n" "> When used, DRS and FRS allow an improved behavior over the CRS mechanism, and eliminate\n" "> its associated periodic polling time of up to 1 second following a reset.\"\n" @@ -67,4 +57,4 @@ "It goes on to say CRS is usually much lower, but doesn't specify an\n" upper bound either. -c744cc980d493ebd8edb9874be3cfc8529684929d0884caf7e9feaa63ed89446 +99550aaf91c3602a828a736482048446f8f3236b528fa9a0c91023e6a4b34846
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.