[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20231130085657.6f7f500cc17b663747e4ee76@linux-foundation.org>
Date: Thu, 30 Nov 2023 08:56:57 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Baoquan He <bhe@...hat.com>
Cc: Arnd Bergmann <arnd@...db.de>, Vivek Goyal <vgoyal@...hat.com>,
linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
x86@...nel.org, linuxppc-dev@...ts.ozlabs.org,
linux-riscv@...ts.infradead.org, linux-s390@...r.kernel.org,
linux-crypto@...r.kernel.org, eric_devolder@...oo.com
Subject: Re: [PATCH 1/2] kexec: fix KEXEC_FILE dependencies
On Thu, 2 Nov 2023 16:03:18 +0800 Baoquan He <bhe@...hat.com> wrote:
> > > CONFIG_KEXEC_FILE, but still get purgatory code built in which is
> > > totally useless.
> > >
> > > Not sure if I think too much over this.
> >
> > I see your point here, and I would suggest changing the
> > CONFIG_ARCH_SUPPORTS_KEXEC_PURGATORY symbol to just indicate
> > the availability of the purgatory code for the arch, rather
> > than actually controlling the code itself. I already mentioned
> > this for s390, but riscv would need the same thing on top.
> >
> > I think the change below should address your concern.
>
> Since no new comment, do you mind spinning v2 to wrap all these up?
This patchset remains in mm-hotfixes-unstable from the previous -rc
cycle. Eric, do you have any comments? Arnd, do you plan on a v2? If
not, should I merge v1? If so, should I now add cc:stable?
Powered by blists - more mailing lists