All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Xueyuan Chen <xueyuan.chen@vivo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 "David Hildenbrand (Arm)" <david@kernel.org>,
	linux-mm@kvack.org, Zi Yan <ziy@nvidia.com>,
	 Baolin Wang <baolin.wang@linux.alibaba.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	 Nico Pache <npache@redhat.com>,
	Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
	 Barry Song <baohua@kernel.org>,
	Lance Yang <lance.yang@linux.dev>,
	 Usama Arif <usama.arif@linux.dev>,
	Kiryl Shutsemau <kas@kernel.org>, Bob Liu <lliubbo@gmail.com>,
	 linux-kernel@vger.kernel.org,
	Xueyuan Chen <xueyuan.chen21@gmail.com>
Subject: Re: [PATCH] mm/huge_memory: fix huge zero folio publication race
Date: Thu, 30 Jul 2026 15:02:37 +0100	[thread overview]
Message-ID: <amtYgCqaMZ0A2UPO@lucifer> (raw)
In-Reply-To: <97d8fa18-cf63-49ee-8ed1-d7e55159566c@vivo.com>

On Thu, Jul 30, 2026 at 09:40:13PM +0800, Xueyuan Chen wrote:
> Thanks all,
>
> I sent this after seeing the Sashiko report for my series and missed
> Lorenzo's earlier fix.
>
> Lorenzo's series supersedes this patch, and 3b77e8c8cde5 is the correct
> Fixes tag.
>
> Please disregard this patch. Sorry for the noise.

Thanks! :)

>
> https://sashiko.dev/#/patchset/20260727143426.1077133-1-xueyuan.chen21@gmail.com
>
> Thanks,
> Xueyuan

Cheers, Lorenzo


      reply	other threads:[~2026-07-30 14:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  4:50 [PATCH] mm/huge_memory: fix huge zero folio publication race xueyuan.chen
2026-07-29  6:44 ` David Hildenbrand (Arm)
2026-07-30  1:02   ` Andrew Morton
2026-07-30  7:27     ` Lorenzo Stoakes (ARM)
2026-07-30 13:40       ` Xueyuan Chen
2026-07-30 14:02         ` Lorenzo Stoakes (ARM) [this message]

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=amtYgCqaMZ0A2UPO@lucifer \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=kas@kernel.org \
    --cc=lance.yang@linux.dev \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lliubbo@gmail.com \
    --cc=npache@redhat.com \
    --cc=ryan.roberts@arm.com \
    --cc=usama.arif@linux.dev \
    --cc=xueyuan.chen21@gmail.com \
    --cc=xueyuan.chen@vivo.com \
    --cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.