diff for duplicates of <5821F701.3080501@redhat.com> diff --git a/a/1.txt b/N1/1.txt index b10f557..9a05b5d 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -111,7 +111,7 @@ for device mmio, then the upper-most address space for device space. Even if platforms use upper-most address space now, it's not rocket science to subtract upper 2M from existing use, then allocate device space from there (downward). ... and if you pull a 'there are systems that have hard-wired addresses -in upper-most 2M', then we can look at if we can quirk these systems, or +in upper-most 2M', then we can look@if we can quirk these systems, or just not support them for this use-case. > The next question is how to tell userspace about all of the reserved diff --git a/a/content_digest b/N1/content_digest index a12595f..d2a81a4 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,31 +1,10 @@ "ref\01478209178-3009-1-git-send-email-eric.auger@redhat.com\0" "ref\020161103220205.37715b49@t450s.home\0" "ref\020161108024559.GA20591@arm.com\0" - "From\0Don Dutile <ddutile@redhat.com>\0" - "Subject\0Re: Summary of LPC guest MSI discussion in Santa Fe\0" + "From\0ddutile@redhat.com (Don Dutile)\0" + "Subject\0Summary of LPC guest MSI discussion in Santa Fe\0" "Date\0Tue, 8 Nov 2016 11:02:09 -0500\0" - "To\0Will Deacon <will.deacon@arm.com>" - " Alex Williamson <alex.williamson@redhat.com>\0" - "Cc\0Eric Auger <eric.auger@redhat.com>" - eric.auger.pro@gmail.com - christoffer.dall@linaro.org - marc.zyngier@arm.com - robin.murphy@arm.com - joro@8bytes.org - tglx@linutronix.de - jason@lakedaemon.net - linux-arm-kernel@lists.infradead.org - kvm@vger.kernel.org - drjones@redhat.com - linux-kernel@vger.kernel.org - pranav.sawargaonkar@gmail.com - iommu@lists.linux-foundation.org - punit.agrawal@arm.com - diana.craciun@nxp.com - benh@kernel.crashing.org - arnd@arndb.de - jcm@redhat.com - " dwmw@amazon.co.uk\0" + "To\0linux-arm-kernel@lists.infradead.org\0" "\00:1\0" "b\0" "On 11/07/2016 09:45 PM, Will Deacon wrote:\n" @@ -141,7 +120,7 @@ "platforms use upper-most address space now, it's not rocket science to subtract\n" "upper 2M from existing use, then allocate device space from there (downward).\n" "... and if you pull a 'there are systems that have hard-wired addresses\n" - "in upper-most 2M', then we can look at if we can quirk these systems, or\n" + "in upper-most 2M', then we can look@if we can quirk these systems, or\n" "just not support them for this use-case.\n" "\n" "> The next question is how to tell userspace about all of the reserved\n" @@ -185,4 +164,4 @@ "> Will\n" > -a8dd1d242bd630ca2eef420d3508a1d99968411c656428b599947b0e3ebb14e3 +4da943901461400620acf6a6328b544113d5f13ddb92eae84424291de75e0e77
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.