[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e7629e1e-ab41-4400-85c4-e3b39cf5be2f@vasilevsky.ca>
Date: Fri, 23 Aug 2024 08:05:43 -0400
From: Dave Vasilevsky <dave@...ilevsky.ca>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>,
Baoquan He <bhe@...hat.com>
Cc: linux-kernel@...r.kernel.org, Michael Ellerman <mpe@...erman.id.au>,
kexec@...ts.infradead.org, debian-powerpc@...ts.debian.org, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-sh@...r.kernel.org,
linux-mips@...r.kernel.org, linux-riscv@...ts.infradead.org,
loongarch@...ts.linux.dev, akpm@...ux-foundation.org, ebiederm@...ssion.com,
hbathini@...ux.ibm.com, piliu@...hat.com, viro@...iv.linux.org.uk,
Sam James <sam@...too.org>
Subject: Re: [PATCH linux-next v3 05/14] crash: clean up kdump related config
items
On 2024-08-23 07:58, Dave Vasilevsky wrote:
> On 2024-08-23 03:16, John Paul Adrian Glaubitz wrote:
>> It should be disabled on m68k and sh by default as well.
>
> Sure, I can change that. What's the reasoning, so I can explain in my commit message?
Oh I don't think m68k even has ARCH_SUPPORTS_CRASH_DUMP, so it will always be off. My question still stands for sh though.
-Dave
Powered by blists - more mailing lists