[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <09c29a3c4879d4ce5d8b97fd60d8ba5e38bed979.camel@physik.fu-berlin.de>
Date: Fri, 23 Aug 2024 20:16:35 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>, Dave Vasilevsky
<dave@...ilevsky.ca>
Cc: bhe@...hat.com, linuxppc-dev@...ts.ozlabs.org, linux-sh@...r.kernel.org,
mpe@...erman.id.au, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, Reimar Döffinger
<Reimar.Doeffinger@....de>
Subject: Re: [PATCH] crash: Default to CRASH_DUMP=n when support for it is
unlikely
Hi Geert,
On Fri, 2024-08-23 at 15:13 +0200, Geert Uytterhoeven wrote:
> IMHO CRASH_DUMP should just default to n, like most kernel options, as
> it enables non-trivial extra functionality: the kernel source tree has
> more than 100 locations that check if CONFIG_CRASH_DUMP is enabled.
I guess we should then revert that part of Baoquan's original patch.
> What is so special about CRASH_DUMP, that it should be enabled by
> default?
Let's ask Baoquan who made the original change to enable CRASH_DUMP by default.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists