From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
x86@kernel.org, Eric Biederman <ebiederm@xmission.com>,
Dave Hansen <dave.hansen@intel.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>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2 0/2] kexec: Remove unnecessary arch hook
Date: Fri, 24 Mar 2023 09:43:00 +0800 [thread overview]
Message-ID: <ZB0AJFCdHcFRI7PE@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230323150755.06f8977fa2b860b8e02c37c3@linux-foundation.org>
On 03/23/23 at 03:07pm, Andrew Morton wrote:
> On Thu, 23 Mar 2023 15:49:20 +0800 Baoquan He <bhe@redhat.com> wrote:
>
> > Hi,
> >
> > On 03/07/23 at 04:44pm, 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.
> > >
> > > v1 is at:
> > > https://lore.kernel.org/all/20221215182339.129803-1-helgaas@kernel.org/
> > >
> > > This v2 is trivially rebased to v6.3-rc1 and the commit log expanded
> > > slightly.
> >
> > This is an obvious and good cleanup patchset, who should I ping to ask
> > for accepting? It's touching kexec generic code, while the hook
> > only exists on x86 ARCH.
>
> I grabbed them
Thanks a lot, Andrew.
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
x86@kernel.org, Eric Biederman <ebiederm@xmission.com>,
Dave Hansen <dave.hansen@intel.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>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH v2 0/2] kexec: Remove unnecessary arch hook
Date: Fri, 24 Mar 2023 09:43:00 +0800 [thread overview]
Message-ID: <ZB0AJFCdHcFRI7PE@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20230323150755.06f8977fa2b860b8e02c37c3@linux-foundation.org>
On 03/23/23 at 03:07pm, Andrew Morton wrote:
> On Thu, 23 Mar 2023 15:49:20 +0800 Baoquan He <bhe@redhat.com> wrote:
>
> > Hi,
> >
> > On 03/07/23 at 04:44pm, 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.
> > >
> > > v1 is at:
> > > https://lore.kernel.org/all/20221215182339.129803-1-helgaas@kernel.org/
> > >
> > > This v2 is trivially rebased to v6.3-rc1 and the commit log expanded
> > > slightly.
> >
> > This is an obvious and good cleanup patchset, who should I ping to ask
> > for accepting? It's touching kexec generic code, while the hook
> > only exists on x86 ARCH.
>
> I grabbed them
Thanks a lot, Andrew.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2023-03-24 1:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 22:44 [PATCH v2 0/2] kexec: Remove unnecessary arch hook Bjorn Helgaas
2023-03-07 22:44 ` Bjorn Helgaas
2023-03-07 22:44 ` [PATCH v2 1/2] x86/kexec: Remove unnecessary arch_kexec_kernel_image_load() Bjorn Helgaas
2023-03-07 22:44 ` Bjorn Helgaas
2023-03-08 10:44 ` Simon Horman
2023-03-08 10:44 ` Simon Horman
2023-03-07 22:44 ` [PATCH v2 2/2] kexec: " Bjorn Helgaas
2023-03-07 22:44 ` Bjorn Helgaas
2023-03-08 10:45 ` Simon Horman
2023-03-08 10:45 ` Simon Horman
2023-03-08 0:37 ` [PATCH v2 0/2] kexec: Remove unnecessary arch hook Baoquan He
2023-03-08 0:37 ` Baoquan He
2023-03-23 7:49 ` Baoquan He
2023-03-23 7:49 ` Baoquan He
2023-03-23 22:07 ` Andrew Morton
2023-03-23 22:07 ` Andrew Morton
2023-03-24 1:43 ` Baoquan He [this message]
2023-03-24 1:43 ` 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=ZB0AJFCdHcFRI7PE@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.