From: Baoquan He <bhe@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Eric Biederman <ebiederm@xmission.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H . Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH 0/2] kexec: Remove unnecessary arch hook
Date: Wed, 21 Dec 2022 14:02:17 +0800 [thread overview]
Message-ID: <Y6KhaSHMsQoT3kfR@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20221217155842.GA389338@bhelgaas>
On 12/17/22 at 09:58am, Bjorn Helgaas wrote:
> On Sat, Dec 17, 2022 at 05:48:51PM +0800, Baoquan He wrote:
> > On 12/15/22 at 12:23pm, Bjorn Helgaas wrote:
> > > From: Bjorn Helgaas <bhelgaas@google.com>
> > >
> > > There are no arch-specific things in arch_kexec_kernel_image_load(), so
> > > remove it and just use the generic version.
> >
> > I ever posted below patch to do the same thing, Andrew only picked the
> > memory leak fixing patch.
> >
> > [PATCH v2 2/2] kexec_file: clean up arch_kexec_kernel_image_load
> > https://lore.kernel.org/all/20220223113225.63106-3-bhe@redhat.com/T/#u
>
> Indeed! Sorry, I wasn't aware of your previous work. If you repost
> it, cc me and I'll be glad to help review it.
When tried to rebase my old patch to the latest kernel, I realized this
patchset is what I can end up with. I would like to ack this patchset
to make it merged. Thanks a lot for the effort.
next prev parent reply other threads:[~2022-12-21 6:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 18:23 [PATCH 0/2] kexec: Remove unnecessary arch hook Bjorn Helgaas
2022-12-15 18:23 ` [PATCH 1/2] x86/kexec: Remove unnecessary arch_kexec_kernel_image_load() Bjorn Helgaas
2022-12-15 18:23 ` [PATCH 2/2] kexec: " Bjorn Helgaas
2022-12-17 9:48 ` [PATCH 0/2] kexec: Remove unnecessary arch hook Baoquan He
2022-12-17 15:58 ` Bjorn Helgaas
2022-12-19 7:01 ` Baoquan He
2022-12-21 6:02 ` Baoquan He [this message]
2022-12-21 6:05 ` Baoquan He
2023-01-04 3:21 ` Baoquan He
2023-01-04 18:37 ` Dave Hansen
2023-01-09 1:38 ` Baoquan He
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=Y6KhaSHMsQoT3kfR@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=ebiederm@xmission.com \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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