From: Andrew Morton <akpm@linux-foundation.org>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Aishwarya TCV <aishwarya.tcv@arm.com>,
<linux-arm-kernel@lists.infradead.org>, <linux-mm@kvack.org>,
Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King <linux@armlinux.org.uk>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/2] arm64: mm: drop VM_FAULT_BADMAP/VM_FAULT_BADACCESS
Date: Wed, 10 Apr 2024 13:18:53 -0700 [thread overview]
Message-ID: <20240410131853.9acbec54873ecb64ab2b3d40@linux-foundation.org> (raw)
In-Reply-To: <8a695c3f-a5eb-4012-a14c-1d76ad79c0dc@huawei.com>
On Wed, 10 Apr 2024 20:48:28 +0800 Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
> > On my JUNO setup, the above patch solves the 'un-killable tests' issues and
> > all the previously failing tests passes. (I have NOT run the full LTP
> > test-suite, though, only replayed the tests that were failing before as
> > mentioned by Aishwarya)
>
> Thanks, I will resend v2, but let's wait for Catalin to see if there is
> any other opinion.
Thanks, I dropped v1.
next prev parent reply other threads:[~2024-04-10 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 8:12 [PATCH -next 0/2] mm: remove arch's private VM_FAULT_BADMAP/BADACCESS Kefeng Wang
2024-04-07 8:12 ` [PATCH 1/2] arm64: mm: drop VM_FAULT_BADMAP/VM_FAULT_BADACCESS Kefeng Wang
2024-04-09 14:28 ` Catalin Marinas
2024-04-10 1:30 ` Kefeng Wang
2024-04-10 10:58 ` Kefeng Wang
2024-04-11 9:59 ` Catalin Marinas
2024-04-11 11:11 ` Kefeng Wang
2024-04-10 11:24 ` Aishwarya TCV
2024-04-10 11:53 ` Kefeng Wang
2024-04-10 12:39 ` Cristian Marussi
2024-04-10 12:48 ` Kefeng Wang
2024-04-10 20:18 ` Andrew Morton [this message]
2024-04-07 8:12 ` [PATCH 2/2] arm: " Kefeng Wang
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=20240410131853.9acbec54873ecb64ab2b3d40@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aishwarya.tcv@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=wangkefeng.wang@huawei.com \
--cc=will@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