From: Andrew Morton <akpm@linux-foundation.org>
To: Weikang Guo <guoweikang.kernel@gmail.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Mike Rapoport <rppt@linux.ibm.com>
Subject: Re: [PATCH] arch/s390: save_area_alloc default failure behavior changed to panic
Date: Thu, 9 Jan 2025 16:43:15 -0800 [thread overview]
Message-ID: <20250109164315.b21f40e1b757b1cf9eb7e042@linux-foundation.org> (raw)
In-Reply-To: <CAOm6qnnxvVfxfoKTj8eO3iqZ9oj__JMJ8o0cH2fZuKkk7gVZYQ@mail.gmail.com>
On Thu, 9 Jan 2025 22:53:57 +0800 Weikang Guo <guoweikang.kernel@gmail.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.
But I'm not sure that we've completed the review discussion of
"mm/memblock: add memblock_alloc_or_panic interface" with Mike?
next prev parent reply other threads:[~2025-01-10 0:43 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
2025-01-10 0:43 ` Andrew Morton [this message]
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=20250109164315.b21f40e1b757b1cf9eb7e042@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agordeev@linux.ibm.com \
--cc=guoweikang.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=rppt@linux.ibm.com \
/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