From: Andrew Morton <akpm@linux-foundation.org>
To: Baoquan He <bhe@redhat.com>
Cc: linux-s390@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
eric_devolder@yahoo.com, linux-riscv@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH 1/2] kexec: fix KEXEC_FILE dependencies
Date: Thu, 30 Nov 2023 08:56:57 -0800 [thread overview]
Message-ID: <20231130085657.6f7f500cc17b663747e4ee76@linux-foundation.org> (raw)
In-Reply-To: <ZUNXxp9AIkjQkP9s@MiWiFi-R3L-srv>
On Thu, 2 Nov 2023 16:03:18 +0800 Baoquan He <bhe@redhat.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?
next prev parent reply other threads:[~2023-11-30 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 11:01 [PATCH 1/2] kexec: fix KEXEC_FILE dependencies Arnd Bergmann
2023-10-23 11:01 ` [PATCH 2/2] kexec: select CRYPTO from KEXEC_FILE instead of depending on it Arnd Bergmann
2023-10-24 3:55 ` Baoquan He
2023-10-24 4:10 ` Baoquan He
2023-10-24 7:09 ` Arnd Bergmann
2023-10-23 15:37 ` [PATCH 1/2] kexec: fix KEXEC_FILE dependencies Conor Dooley
2023-10-23 16:04 ` Arnd Bergmann
2023-10-23 16:12 ` Conor Dooley
2023-10-24 12:44 ` Baoquan He
2023-10-24 13:17 ` Arnd Bergmann
2023-10-25 9:58 ` Baoquan He
2023-10-25 12:59 ` Eric DeVolder
2023-11-02 8:03 ` Baoquan He
2023-11-30 16:56 ` Andrew Morton [this message]
2023-11-30 20:54 ` Eric DeVolder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231130085657.6f7f500cc17b663747e4ee76@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=eric_devolder@yahoo.com \
--cc=kexec@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).