diff for duplicates of <20200505201522.GA683243@linux.ibm.com> diff --git a/a/content_digest b/N1/content_digest index 56a42fb..4d98a64 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -10,16 +10,19 @@ "Subject\0Re: [PATCH v2 17/20] mm: free_area_init: allow defining max_zone_pfn in descending order\0" "Date\0Tue, 5 May 2020 23:15:22 +0300\0" "To\0Vineet Gupta <Vineet.Gupta1@synopsys.com>\0" - "Cc\0Rich Felker <dalias@libc.org>" + "Cc\0Mike Rapoport <rppt@kernel.org>" + Guenter Roeck <linux@roeck-us.net> + Rich Felker <dalias@libc.org> linux-ia64@vger.kernel.org <linux-ia64@vger.kernel.org> linux-doc@vger.kernel.org <linux-doc@vger.kernel.org> Catalin Marinas <catalin.marinas@arm.com> Heiko Carstens <heiko.carstens@de.ibm.com> + x86@kernel.org <x86@kernel.org> Michal Hocko <mhocko@kernel.org> James E.J. Bottomley <James.Bottomley@hansenpartnership.com> Max Filippov <jcmvbkbc@gmail.com> Guo Ren <guoren@kernel.org> - linux-csky@vger.kernel.org <linux-csky@vger.kernel.org> + Ley Foon Tan <ley.foon.tan@intel.com> sparclinux@vger.kernel.org <sparclinux@vger.kernel.org> linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> Greg Ungerer <gerg@linux-m68k.org> @@ -28,7 +31,12 @@ linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org> Baoquan He <bhe@redhat.com> Jonathan Corbet <corbet@lwn.net> - " linux-sh@vger.kerne\0" + linux-hexagon@vger.kernel.org <linux-hexagon@vger.kernel.org> + Helge Deller <deller@gmx.de> + linux-sh@vger.kernel.org <linux-sh@vger.kernel.org> + Russell King <linux@armlinux.org.uk> + linux-csky@vger.kernel.org <linux-csky@vger.kernel.org> + " Geert Uytterhoeven <geert@linux-m68k.org>\0" "\00:1\0" "b\0" "On Tue, May 05, 2020 at 06:07:46PM +0000, Vineet Gupta wrote:\n" @@ -93,4 +101,4 @@ "Sincerely yours,\n" Mike. -0ee6cad439387da8a58a46246856796a70d8e53cd7e9f578b815132d7bea4168 +e533193ea0090b7b9dafa677b67a61c11ab2e23f2c2770277d778378294801dc
diff --git a/a/content_digest b/N2/content_digest index 56a42fb..44f592a 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -8,7 +8,7 @@ "ref\088b9465b-6e6d-86ca-3776-ccb7a5b60b7f@synopsys.com\0" "From\0Mike Rapoport <rppt@linux.ibm.com>\0" "Subject\0Re: [PATCH v2 17/20] mm: free_area_init: allow defining max_zone_pfn in descending order\0" - "Date\0Tue, 5 May 2020 23:15:22 +0300\0" + "Date\0Tue, 05 May 2020 20:15:22 +0000\0" "To\0Vineet Gupta <Vineet.Gupta1@synopsys.com>\0" "Cc\0Rich Felker <dalias@libc.org>" linux-ia64@vger.kernel.org <linux-ia64@vger.kernel.org> @@ -93,4 +93,4 @@ "Sincerely yours,\n" Mike. -0ee6cad439387da8a58a46246856796a70d8e53cd7e9f578b815132d7bea4168 +af46995184788c336b82d067ff28c946f452e748c54a74beeacb5629af109981
diff --git a/a/content_digest b/N3/content_digest index 56a42fb..7bc00b7 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -28,7 +28,15 @@ linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org> Baoquan He <bhe@redhat.com> Jonathan Corbet <corbet@lwn.net> - " linux-sh@vger.kerne\0" + linux-sh@vger.kernel.org <linux-sh@vger.kernel.org> + linux-hexagon@vger.kernel.org <linux-hexagon@vger.kernel.org> + Helge Deller <deller@gmx.de> + x86@kernel.org <x86@kernel.org> + Russell King <linux@armlinux.org.uk> + Ley Foon Tan <ley.foon.tan@intel.com> + Geert Uytterhoeven <geert@linux-m68k.org> + Guenter Roeck <linux@roeck-us.net> + " Mike Rapoport <rppt@kernel.org>\0" "\00:1\0" "b\0" "On Tue, May 05, 2020 at 06:07:46PM +0000, Vineet Gupta wrote:\n" @@ -93,4 +101,4 @@ "Sincerely yours,\n" Mike. -0ee6cad439387da8a58a46246856796a70d8e53cd7e9f578b815132d7bea4168 +58e38eb89f74179ef9eb93fe2e1312a2d7b117abb5c95ece5565d8d37463513e
diff --git a/a/1.txt b/N4/1.txt index b4f6324..55c4153 100644 --- a/a/1.txt +++ b/N4/1.txt @@ -18,7 +18,7 @@ On Tue, May 05, 2020 at 06:07:46PM +0000, Vineet Gupta wrote: > > 0x1_0000_0000 - <end of DDR 2 bank> > > We don't have such a system, but it is indeed possible in theory. The question is -> - Can other arches have such a setup too +> �- Can other arches have such a setup too At the moment all architectures that support HIGHMEM have it above DMA/NORMAL. I'm not sure if such a setup is theoretically possible for @@ -31,7 +31,7 @@ The general case is somewhat like And of course, either max_dma_pfn or max_high_pfn or both may be not needed for an architecture. -> - Is it not better to have the core retain the flexibility just in case +> �- Is it not better to have the core retain the flexibility just in case Hmm, there is indeed flexibility in the nodes and zones initialization, but if you'd look more closely to free_area_init*() and friends, there diff --git a/a/content_digest b/N4/content_digest index 56a42fb..2b64334 100644 --- a/a/content_digest +++ b/N4/content_digest @@ -10,16 +10,19 @@ "Subject\0Re: [PATCH v2 17/20] mm: free_area_init: allow defining max_zone_pfn in descending order\0" "Date\0Tue, 5 May 2020 23:15:22 +0300\0" "To\0Vineet Gupta <Vineet.Gupta1@synopsys.com>\0" - "Cc\0Rich Felker <dalias@libc.org>" + "Cc\0Mike Rapoport <rppt@kernel.org>" + Guenter Roeck <linux@roeck-us.net> + Rich Felker <dalias@libc.org> linux-ia64@vger.kernel.org <linux-ia64@vger.kernel.org> linux-doc@vger.kernel.org <linux-doc@vger.kernel.org> Catalin Marinas <catalin.marinas@arm.com> Heiko Carstens <heiko.carstens@de.ibm.com> + x86@kernel.org <x86@kernel.org> Michal Hocko <mhocko@kernel.org> James E.J. Bottomley <James.Bottomley@hansenpartnership.com> Max Filippov <jcmvbkbc@gmail.com> Guo Ren <guoren@kernel.org> - linux-csky@vger.kernel.org <linux-csky@vger.kernel.org> + Ley Foon Tan <ley.foon.tan@intel.com> sparclinux@vger.kernel.org <sparclinux@vger.kernel.org> linux-riscv@lists.infradead.org <linux-riscv@lists.infradead.org> Greg Ungerer <gerg@linux-m68k.org> @@ -28,7 +31,12 @@ linux-c6x-dev@linux-c6x.org <linux-c6x-dev@linux-c6x.org> Baoquan He <bhe@redhat.com> Jonathan Corbet <corbet@lwn.net> - " linux-sh@vger.kerne\0" + linux-hexagon@vger.kernel.org <linux-hexagon@vger.kernel.org> + Helge Deller <deller@gmx.de> + linux-sh@vger.kernel.org <linux-sh@vger.kernel.org> + Russell King <linux@armlinux.org.uk> + linux-csky@vger.kernel.org <linux-csky@vger.kernel.org> + " Geert Uytterhoeven <geert@linux-m68k.org>\0" "\00:1\0" "b\0" "On Tue, May 05, 2020 at 06:07:46PM +0000, Vineet Gupta wrote:\n" @@ -51,7 +59,7 @@ "> > 0x1_0000_0000 - <end of DDR 2 bank>\n" "> \n" "> We don't have such a system, but it is indeed possible in theory. The question is\n" - "> \302\240- Can other arches have such a setup too\n" + "> \303\257\302\277\302\275- Can other arches have such a setup too\n" "\n" "At the moment all architectures that support HIGHMEM have it above\n" "DMA/NORMAL. I'm not sure if such a setup is theoretically possible for\n" @@ -64,7 +72,7 @@ "And of course, either max_dma_pfn or max_high_pfn or both may be not\n" "needed for an architecture.\n" "\n" - "> \302\240- Is it not better to have the core retain the flexibility just in case\n" + "> \303\257\302\277\302\275- Is it not better to have the core retain the flexibility just in case\n" "\n" "Hmm, there is indeed flexibility in the nodes and zones initialization,\n" "but if you'd look more closely to free_area_init*() and friends, there\n" @@ -93,4 +101,4 @@ "Sincerely yours,\n" Mike. -0ee6cad439387da8a58a46246856796a70d8e53cd7e9f578b815132d7bea4168 +a967e281ed364fae5367b2bbc0af7898e056947d8453aa2801466e8bc6578821
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.