From: Andrew Morton <akpm@linux-foundation.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
ljs@kernel.org, ziy@nvidia.com, baolin.wang@linux.alibaba.com,
liam@infradead.org, npache@redhat.com, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH mm-unstable 1/1] mm/khugepaged: fix PMD collapse swap PTE accounting
Date: Tue, 9 Jun 2026 11:56:10 -0700 [thread overview]
Message-ID: <20260609115610.9a62a2dbb814bb9d5a19ac2e@linux-foundation.org> (raw)
In-Reply-To: <71507be5-8430-4a3d-af80-6777a421565e@linux.dev>
On Tue, 9 Jun 2026 21:56:13 +0800 Lance Yang <lance.yang@linux.dev> wrote:
> >> Signed-off-by: Lance Yang <lance.yang@linux.dev>
> >> ---
> >> Sent separately, as discussed in [1], to spell out the PMD-order swap PTE
> >> case. Patch [2] is still only in mm-unstable, so no Fixes: tag.
> >
> > Right, probably we just want to add the Fixes: tag once Andrew moves the series
> > to mm-stable?
>
> Yep, hopefully Andrew can add the Fixes: tag when applying this, once
> the series lands in mm-stable.
No probs.
> Should be soon, I guess :P
I move the second batch into mm-stable after Linus has merged the first
batch, usually.
next prev parent reply other threads:[~2026-06-09 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 12:04 Lance Yang
2026-06-09 13:16 ` David Hildenbrand (Arm)
2026-06-09 14:33 ` Lorenzo Stoakes
2026-06-09 16:28 ` Lance Yang
2026-06-09 17:04 ` Nico Pache
2026-06-10 2:10 ` Lance Yang
2026-06-13 2:02 ` Wei Yang
2026-06-09 13:20 ` David Hildenbrand (Arm)
2026-06-09 13:56 ` Lance Yang
2026-06-09 18:56 ` Andrew Morton [this message]
2026-06-10 1:52 ` Lance Yang
2026-06-09 14:32 ` Lorenzo Stoakes
2026-06-09 17:08 ` Nico Pache
2026-06-10 8:02 ` Baolin Wang
2026-06-13 1:59 ` Wei Yang
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=20260609115610.9a62a2dbb814bb9d5a19ac2e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®