From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Walmsley <pjw@kernel.org>
Cc: Vivian Wang <wangruikang@iscas.ac.cn>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alexandre Ghiti <alex@ghiti.fr>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4] riscv: mm: Avoid spurious fault after hotplugging vmemmap
Date: Thu, 9 Jul 2026 19:34:37 -0700 [thread overview]
Message-ID: <20260709193437.701fac04e878b34d75ab101b@linux-foundation.org> (raw)
In-Reply-To: <b7ab255d-8d0a-24f7-2953-4f5decf11432@kernel.org>
On Thu, 9 Jul 2026 20:00:08 -0600 (MDT) Paul Walmsley <pjw@kernel.org> wrote:
> Hi Andrew,
>
> On Tue, 30 Jun 2026, Andrew Morton wrote:
>
> > On Wed, 1 Jul 2026 13:01:15 +0800 Vivian Wang <wangruikang@iscas.ac.cn> wrote:
> >
> > > which made it miss:
> > >
> > > Changes in v4:
> > > - Rebase on v7.2-rc1, drop dependencies
> > > - (No code changes otherwise)
> > > - (A concurrency fix for mark_new_valid_map was sent independently)
> > > https://lore.kernel.org/linux-riscv/20260629-riscv-mm-new-valid-map-ordering-v1-1-60d8c10c6292@iscas.ac.cn/
> > > ^--- this
> >
> > Cool, I grabbed that. Same caveats: riscv maintainers, please?
>
> I just responded to Vivian's v5. I guess he'll probably do a v6, at which
> point, will plan to queue it for v7.2-rc here, unless you have any
> objections?
Go for it, thanks.
When I see a version of this pop up in linux-next I'll drop the mm.git
copy. This is my standard procedure.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-07-10 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 7:51 [PATCH v4] riscv: mm: Avoid spurious fault after hotplugging vmemmap Vivian Wang
2026-07-01 4:11 ` Andrew Morton
2026-07-01 5:01 ` Vivian Wang
2026-07-01 5:33 ` Andrew Morton
2026-07-10 2:00 ` Paul Walmsley
2026-07-10 2:34 ` Andrew Morton [this message]
2026-07-06 3:00 ` Muchun Song
2026-07-06 5:04 ` Vivian Wang
2026-07-06 5:38 ` Muchun Song
2026-07-06 5:48 ` Vivian 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=20260709193437.701fac04e878b34d75ab101b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=wangruikang@iscas.ac.cn \
/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