[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180207104111.sljc62bgkggmtio4@node.shutemov.name>
Date: Wed, 7 Feb 2018 13:41:11 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Dou Liyang <douly.fnst@...fujitsu.com>
Cc: Mike Galbraith <efault@....de>, Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Baoquan He <bhe@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dave Young <dyoung@...hat.com>, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>, linux-mm@...ck.org,
Vivek Goyal <vgoyal@...hat.com>,
Cyrill Gorcunov <gorcunov@...nvz.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...e.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Subject: Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at
runtime for CONFIG_SPARSEMEM_EXTREME=y
On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote:
> Hi All,
>
> I met the makedumpfile failed in the upstream kernel which contained
> this patch. Did I missed something else?
None I'm aware of.
Is there a reason to suspect that the issue is related to the bug this patch
fixed?
--
Kirill A. Shutemov
Powered by blists - more mailing lists