From: Weikang Guo <guoweikang.kernel@gmail.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] arch/s390: save_area_alloc default failure behavior changed to panic
Date: Thu, 9 Jan 2025 22:53:57 +0800 [thread overview]
Message-ID: <CAOm6qnnxvVfxfoKTj8eO3iqZ9oj__JMJ8o0cH2fZuKkk7gVZYQ@mail.gmail.com> (raw)
In-Reply-To: <Z3/VoAaSQF5Tcy4t@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com>
Alexander Gordeev <agordeev@linux.ibm.com> wrote on Thursday, 9
January 2025 21:56:
>
> On Thu, Jan 09, 2025 at 04:28:06PM +0800, Weikang Guo wrote:
> > > This patch is a follow-up to v7, but instead it needs to be part of v8.
> > > I guess Andrew would refresh mm-everything (or whatever he finds appropriate)
> > > with the new version.
> >
> > Sorry to confuse you, `memblock_alloc_or_panic` is already merged
> > into mm/mm-everything
> > by Andrew, so this is an additional patch specifically to fix the
> > problem you mentioned.
> >
> > This patch is based on the latest mm/mm-everything branch, and it has
> > also been merged
> > by Andrew,You should have received the email.
> >
> > @Alexander I hope I cleared your confusion. ^ ^
>
> I do not think I am confused. The merged patch is not good enough for s390.
> This patch addresses my comments, but it needs to be merged into v7 or re-
> posted as v8.
>
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.
> > > @Andrew, please correct me if I am wrong.
> > >
> > > Thanks!
> >
> >
> > Best regards.
> > ---
> > Guo
>
> Thanks!
---
Guo
next prev parent reply other threads:[~2025-01-09 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 3:31 Guo Weikang
2025-01-09 8:08 ` Alexander Gordeev
2025-01-09 8:28 ` Weikang Guo
2025-01-09 13:56 ` Alexander Gordeev
2025-01-09 14:53 ` Weikang Guo [this message]
2025-01-10 0:43 ` Andrew Morton
2025-01-10 6:48 ` Weikang Guo
2025-01-10 7:45 ` Alexander Gordeev
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=CAOm6qnnxvVfxfoKTj8eO3iqZ9oj__JMJ8o0cH2fZuKkk7gVZYQ@mail.gmail.com \
--to=guoweikang.kernel@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.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