[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOm6qnkC=TLm+2hDi-T+C54NY4_+yFEpNhssj3wvaTfewJz4vw@mail.gmail.com>
Date: Fri, 10 Jan 2025 14:48:01 +0800
From: Weikang Guo <guoweikang.kernel@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Alexander Gordeev <agordeev@...ux.ibm.com>, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Mike Rapoport <rppt@...ux.ibm.com>
Subject: Re: [PATCH] arch/s390: save_area_alloc default failure behavior
changed to panic
Andrew Morton <akpm@...ux-foundation.org> wrote on Friday, 10 January
2025 08:43:
>
> On Thu, 9 Jan 2025 22:53:57 +0800 Weikang Guo <guoweikang.kernel@...il.com> wrote:
>
> > I understand your point, you want to modify directly based on the
> > original patch.
> > If we repost it,it may not be v8 but v9.
> >
> > Last v8 patch: https://lkml.kernel.org/r/20250102072528.650926-1-guoweikang.kernel@gmail.com
> >
> > I reduced the recipients for V8 because I remembered that the number
> > of CCs might
> > have exceeded the limit at the time, and there hadn't been any
> > comments on V7 for a long time
> >
> > > @Andrew, is that still possible?
> >
> > @Andrew, I can cooperate if necessary, I could merge them into one
> > patch and repost.
>
> I'll fold this patch ("arch/s390: save_area_alloc default failure
> behavior changed to panic") into
> "mm-memblock-add-memblock_alloc_or_panic-interface.patch", v8 before
> sending the latter upstream.
>
Andrew, I appreciate your help with this!
> But I'm not sure that we've completed the review discussion of
> "mm/memblock: add memblock_alloc_or_panic interface" with Mike?
Here is Mike's latest feedback on the patch, I have recorded it in the
v8 changelog:
Acked-by: Mike Rapoport (Microsoft) <rppt@...nel.org>
Links: https://lore.kernel.org/lkml/Z2fknmnNtiZbCc7x@kernel.org/
Thanks!
---
Guo
Powered by blists - more mailing lists