From: Alexander Gordeev <agordeev@linux.ibm.com>
To: Weikang Guo <guoweikang.kernel@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: 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 14:56:48 +0100 [thread overview]
Message-ID: <Z3/VoAaSQF5Tcy4t@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com> (raw)
In-Reply-To: <CAOm6qnkoKjrUXCbhCiSYviuwCRVES1FYCy17fwATtyZ+M=Aw7g@mail.gmail.com>
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.
@Andrew, is that still possible?
> > @Andrew, please correct me if I am wroing.
> >
> > Thanks!
>
>
> Best regards.
> ---
> Guo
Thanks!
next prev parent reply other threads:[~2025-01-09 13:56 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 [this message]
2025-01-09 14:53 ` Weikang Guo
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=Z3/VoAaSQF5Tcy4t@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com \
--to=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=guoweikang.kernel@gmail.com \
--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