[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250304154353.a79c330bffb4d21dce2dad9c@linux-foundation.org>
Date: Tue, 4 Mar 2025 15:43:53 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Baoquan He <bhe@...hat.com>
Cc: "Kirill A. Shutemov" <kirill@...temov.name>, ebiederm@...ssion.com,
kexec@...ts.infradead.org, Yan Zhao <yan.y.zhao@...el.com>,
linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev, x86@...nel.org,
rick.p.edgecombe@...el.com, kirill.shutemov@...ux.intel.com
Subject: Re: [PATCH v2 0/1] Accept unaccepted kexec segments' destination
addresses
On Mon, 13 Jan 2025 19:12:27 +0800 Baoquan He <bhe@...hat.com> wrote:
> On 01/13/25 at 12:01pm, Kirill A. Shutemov wrote:
> > On Fri, Dec 13, 2024 at 05:49:30PM +0800, Yan Zhao wrote:
> > > Hi Eric,
> > >
> > > This is a repost of the patch "kexec_core: Accept unaccepted kexec
> > > destination addresses" [1], rebased to v6.13-rc2.
> >
> > Can we get this patch applied?
>
> This looks good to me. In v1, we have analyzed all other possible
> solutions, however change in this patch seems the simplest and most
> accepatable one.
>
> If Eric has no objection, maybe Andrew can help pick this into his tree.
OK, but that patch is the only thing in the world which is older than me.
Yan, can you please refresh, retest and resend?
Also, please consolidate the changelogging into a single email -
a single-patch series with a coverletter is just weird.
Putting the [0/n] info into the singleton patch's changelog is more
reader-friendly, and that's what counts, no?
Thanks.
Powered by blists - more mailing lists