Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <ljs@kernel.org>
To: Nico Pache <npache@redhat.com>
Cc: Lance Yang <lance.yang@linux.dev>,
	akpm@linux-foundation.org,  ziy@nvidia.com,
	baolin.wang@linux.alibaba.com, Liam.Howlett@oracle.com,
	 ryan.roberts@arm.com, dev.jain@arm.com, baohua@kernel.org,
	richard.weiyang@gmail.com,  linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, david@kernel.org
Subject: Re: [PATCH mm-new v3 3/3] mm/khugepaged: merge PTE scanning logic into a new helper
Date: Thu, 18 Jun 2026 15:34:05 +0100	[thread overview]
Message-ID: <ajQBSh7RvRVr-BmO@lucifer> (raw)
In-Reply-To: <CAA1CXcA581SeWTWOz=Kcrw=LW5tshzWyNZMtCnn-X5PrZ0RFVg@mail.gmail.com>

On Thu, Jun 18, 2026 at 07:19:41AM -0600, Nico Pache wrote:
>
> I have a work-in-progress series to address a number of cleanups, the
> code should be ready at the start of next week. I just want to test
> and verify things first, and it's best not to post at the end of the
> week :)

Woo! Thanks :) Cleanups very welcome.

But yeah best to send on week of -rc1 please. I'm holding off on a pretty
large series myself and we need to get into the habit of treating the merge
window as quiet time.

I think Andrew is not taking anything atm anyway and asking people to
resend in -rc1 anyway.

(There's a debate as to - send early, get early feedback, resend in -rc1
vs. tidal wave in -rc1, but I'm kinda in favour of the tidal wave, as it at
least gives some breathing space. I am very very far behind on review rn :)

Thanks, Lorenzo


  reply	other threads:[~2026-06-18 14:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  4:37 [PATCH mm-new v3 0/3] refactor and merge PTE scanning logic Lance Yang
2025-10-08  4:37 ` [PATCH mm-new v3 1/3] mm/khugepaged: optimize PTE scanning with if-else-if-else-if chain Lance Yang
2025-10-14 12:17   ` Lorenzo Stoakes
2025-10-14 12:27     ` David Hildenbrand
2025-10-15  4:49       ` Lance Yang
2025-10-15  9:16         ` Lorenzo Stoakes
2025-10-15  9:31           ` Lance Yang
2025-10-08  4:37 ` [PATCH mm-new v3 2/3] mm/khugepaged: use VM_WARN_ON_FOLIO instead of VM_BUG_ON_FOLIO for non-anon folios Lance Yang
2025-10-14 12:25   ` Lorenzo Stoakes
2025-10-08  4:37 ` [PATCH mm-new v3 3/3] mm/khugepaged: merge PTE scanning logic into a new helper Lance Yang
2025-10-09  1:07   ` Andrew Morton
2025-10-09  1:49     ` Lance Yang
2025-10-10  9:10   ` Dev Jain
2025-10-10 10:42     ` Lance Yang
2025-10-10 13:29   ` Wei Yang
2025-10-10 13:55     ` Lance Yang
2025-10-14 12:36   ` Lorenzo Stoakes
2026-06-18 12:22     ` Nico Pache
2026-06-18 13:10       ` Lance Yang
2026-06-18 13:19         ` Nico Pache
2026-06-18 14:34           ` Lorenzo Stoakes [this message]
2025-10-14 17:41   ` Lorenzo Stoakes
2025-10-15  1:48     ` Lance 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=ajQBSh7RvRVr-BmO@lucifer \
    --to=ljs@kernel.org \
    --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=lance.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npache@redhat.com \
    --cc=richard.weiyang@gmail.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