[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231124084441.b913fc404fec53d5d0946c55@linux-foundation.org>
Date: Fri, 24 Nov 2023 08:44:41 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Baoquan He <bhe@...hat.com>
Cc: Ignat Korchagin <ignat@...udflare.com>,
linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org, linux-s390@...r.kernel.org,
eric_devolder@...oo.com, kernel-team <kernel-team@...udflare.com>
Subject: Re: [PATCH 2/3] drivers/base/cpu: crash data showing should depends
on KEXEC_CORE
On Thu, 23 Nov 2023 19:15:43 +0800 Baoquan He <bhe@...hat.com> wrote:
> > > CONFIG_KEXEC is used to enable kexec_load interface, the
> > > crash_notes/crash_notes_size/crash_hotplug showing depends on
> > > CONFIG_KEXEC is incorrect. It should depend on KEXEC_CORE instead.
> > >
> > > Fix it now.
> >
> > Can we add Fixes/CC stable, so it gets eventually backported into 6.6?
>
> Makes sense. Will add it in v2 since I need respin to add the missing
> stuff in patch 1. Thanks.
Please avoid mixing cc:stable patches and this-merge-window fixes in
the same series as next-merge-window material. Because I'll just have
to separate them out anyway, causing what-I-merged to unnecessarily
differ from what-you-sent.
Powered by blists - more mailing lists