Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vivian Wang <wangruikang@iscas.ac.cn>,
	Paul Walmsley <pjw@kernel.org>,
	 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 20:00:08 -0600 (MDT)	[thread overview]
Message-ID: <b7ab255d-8d0a-24f7-2953-4f5decf11432@kernel.org> (raw)
In-Reply-To: <20260630223332.534218a41b2f574de327e4db@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

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?

Thanks for helping out on this one,


- Paul

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-07-10  2:00 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 [this message]
2026-07-10  2:34         ` Andrew Morton
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=b7ab255d-8d0a-24f7-2953-4f5decf11432@kernel.org \
    --to=pjw@kernel.org \
    --cc=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=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