Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Usama Arif <usama.arif@linux.dev>,
	david@kernel.org, chrisl@kernel.org, kasong@tencent.com,
	ziy@nvidia.com, linux-mm@kvack.org, ying.huang@linux.alibaba.com,
	Baoquan He <baoquan.he@linux.dev>,
	willy@infradead.org, youngjun.park@lge.com, hannes@cmpxchg.org,
	riel@surriel.com, shakeel.butt@linux.dev, alex@ghiti.fr,
	kas@kernel.org, baohua@kernel.org, dev.jain@arm.com,
	baolin.wang@linux.alibaba.com, npache@redhat.com,
	"Liam R. Howlett" <liam@infradead.org>,
	ryan.roberts@arm.com, Vlastimil Babka <vbabka@kernel.org>,
	lance.yang@linux.dev, linux-kernel@vger.kernel.org,
	nphamcs@gmail.com, shikemeng@huaweicloud.com,
	kernel-team@meta.com
Subject: Re: [PATCH 0/6] mm: preparatory patches for PMD level swap entries
Date: Sat, 4 Jul 2026 13:04:02 +0300	[thread overview]
Message-ID: <akjakkURVyM4x1dt@kernel.org> (raw)
In-Reply-To: <20260703194502.102044-1-sj@kernel.org>

Hi SJ,

On Fri, Jul 03, 2026 at 12:45:01PM -0700, SJ Park wrote:
> On Thu, 2 Jul 2026 16:08:03 +0300 Mike Rapoport <rppt@kernel.org> wrote:
> > 
> > CI grabs patches from patchwork and tries to apply them to one of the three
> > bases: mm-unstable, mm-new or the latest Linus' commit merged into mm.git.
> > 
> > If patches apply, the other bases are not checked. 
> > 
> > This patches applied cleanly to mm-unstable and successfully passed (at
> > least once :) )
> > https://github.com/linux-mm/linux-mm/actions/runs/28544575927/
> 
> Awesome!
> 
> I found the CI script (mm-ci) on the GitHub organization.  Is the repo open to
> contributions?

Yes :)

> If so, between GitHub PR and patches to linux-mm@ what is more
> preferred?

The way it works, all testing update should go to mm-ci. There is a bot
that takes them from there and generates PRs inn linux-mm that include
patches and the CI files.

> Seems it is not running DAMON specific tests, and I want to add
> DAMON kunit test to the test set as a first step (DAMO selftest is bit flaky on
> some systems), if people don't mind.

Patches are welcome :)

If DAMON selftest is flaky let's keep it out for now please, otherwise it
would cause too much noise.
 
> I or someone else may also want to add more tests like Cc list checking [1] in
> future.
> 
> [1] https://lore.kernel.org/20260703190421.100480-1-sj@kernel.org

Yeah, I think it would be helpful. 

> Thanks,
> SJ

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2026-07-04 10:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 16:34 [PATCH 0/6] mm: preparatory patches for PMD level swap entries Usama Arif
2026-06-30 16:34 ` [PATCH 1/6] mm: add softleaf_to_pmd() and convert existing callers Usama Arif
2026-07-03 10:21   ` Lance Yang
2026-06-30 16:34 ` [PATCH 2/6] mm: extract mm_prepare_for_swap_entries() helper Usama Arif
2026-07-01 16:56   ` David Hildenbrand (Arm)
2026-06-30 16:34 ` [PATCH 3/6] fs/proc: use softleaf_has_pfn() in pagemap PMD walker Usama Arif
2026-06-30 16:34 ` [PATCH 4/6] mm/huge_memory: move softleaf_to_folio() inside migration branch Usama Arif
2026-06-30 16:34 ` [PATCH 5/6] mm/migrate_device: move softleaf_to_folio() inside device-private branch Usama Arif
2026-07-01 19:40   ` David Hildenbrand (Arm)
2026-06-30 16:34 ` [PATCH 6/6] mm: rename ARCH_ENABLE_THP_MIGRATION to ARCH_SUPPORTS_PMD_SOFTLEAF Usama Arif
2026-07-01 20:03   ` David Hildenbrand (Arm)
2026-07-02 16:55     ` Lorenzo Stoakes
2026-06-30 19:50 ` [PATCH 0/6] mm: preparatory patches for PMD level swap entries Andrew Morton
2026-07-01  8:04   ` Lorenzo Stoakes
     [not found]     ` <20260701164613.008aa13cb6187ec9597bf652@linux-foundation.org>
     [not found]       ` <akY_L-yuaCXBOXb3@lucifer>
     [not found]         ` <akZis7j6xSjl8K_D@kernel.org>
2026-07-02 16:53           ` Lorenzo Stoakes
2026-07-02 16:57             ` Mark Brown
2026-07-02 17:08               ` Lorenzo Stoakes
2026-07-02 17:10                 ` David Hildenbrand (Arm)
2026-07-02 17:21                   ` Lorenzo Stoakes
2026-07-03 19:45           ` SJ Park
2026-07-04 10:04             ` Mike Rapoport [this message]
2026-07-01 10:44   ` Usama Arif
2026-07-01 14:09   ` Usama Arif
2026-07-01 20:04 ` David Hildenbrand (Arm)
2026-07-03 17:48 ` Usama Arif

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=akjakkURVyM4x1dt@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=baoquan.he@linux.dev \
    --cc=chrisl@kernel.org \
    --cc=david@kernel.org \
    --cc=dev.jain@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=kas@kernel.org \
    --cc=kasong@tencent.com \
    --cc=kernel-team@meta.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=nphamcs@gmail.com \
    --cc=riel@surriel.com \
    --cc=ryan.roberts@arm.com \
    --cc=shakeel.butt@linux.dev \
    --cc=shikemeng@huaweicloud.com \
    --cc=sj@kernel.org \
    --cc=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --cc=willy@infradead.org \
    --cc=ying.huang@linux.alibaba.com \
    --cc=youngjun.park@lge.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