From: Harry Yoo <harry.yoo@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Liam.Howlett@oracle.com,
akpm@linux-foundation.org, baohua@kernel.org,
baolin.wang@linux.alibaba.com, david@kernel.org,
dev.jain@arm.com, hughd@google.com, jane.chu@oracle.com,
jannh@google.com, kas@kernel.org, lance.yang@linux.dev,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
npache@redhat.com, pfalcato@suse.de, ryan.roberts@arm.com,
vbabka@suse.cz, ziy@nvidia.com
Subject: Re: [PATCH V2 5.4.y 0/2] Fix bad pmd due to race between change_prot_numa() and THP migration
Date: Fri, 9 Jan 2026 10:43:19 +0900 [thread overview]
Message-ID: <aWBdN9TdV2n8QfsY@hyeyoo> (raw)
In-Reply-To: <2026010836-abdomen-drilling-6326@gregkh>
On Thu, Jan 08, 2026 at 02:49:49PM +0100, Greg KH wrote:
> On Wed, Jan 07, 2026 at 12:25:57PM +0900, Harry Yoo wrote:
> > V1 -> V2:
> > - Because `pmd_val` variable broke ppc builds due to its name,
> > renamed it to `_pmd`. see [1].
> > [1] https://lore.kernel.org/stable/aS7lPZPYuChOTdXU@hyeyoo
> >
> > - Added David Hildenbrand's Acked-by [2], thanks a lot!
> > [2] https://lore.kernel.org/linux-mm/ac8d7137-3819-4a75-9dd3-fb3d2259ebe4@kernel.org/
> >
> > # TL;DR
> >
> > previous discussion: https://lore.kernel.org/linux-mm/20250921232709.1608699-1-harry.yoo@oracle.com/
>
> 5.4.y is end-of-life, sorry.
Oh.
It became EOL last month and I didn't notice that.
No problem, thanks!
--
Cheers,
Harry / Hyeonggon
prev parent reply other threads:[~2026-01-09 1:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 3:25 Harry Yoo
2026-01-07 3:25 ` [PATCH V2 5.4.y 1/2] mm/mprotect: use long for page accountings and retval Harry Yoo
2026-01-07 3:25 ` [PATCH V2 5.4.y 2/2] mm/mprotect: delete pmd_none_or_clear_bad_unless_trans_huge() Harry Yoo
2026-01-08 13:49 ` [PATCH V2 5.4.y 0/2] Fix bad pmd due to race between change_prot_numa() and THP migration Greg KH
2026-01-09 1:43 ` Harry Yoo [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=aWBdN9TdV2n8QfsY@hyeyoo \
--to=harry.yoo@oracle.com \
--cc=Liam.Howlett@oracle.com \
--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=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=jane.chu@oracle.com \
--cc=jannh@google.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=pfalcato@suse.de \
--cc=ryan.roberts@arm.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox