From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C6D82317147 for ; Thu, 2 Jul 2026 13:08:16 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782997697; cv=none; b=gt9ydV8y96+H7B/wtJE7EenKANoHdgLDNrpsU8VH7xMrGJvI3T+qNonaz3+6wc2XDOy/Kyj8u00Q8AAGmmV+atosOYQ007wVGL3O0l41g7Z3YZQVO6yOSuKM37Wiah1g3Jtp3lUTt/TtTNGCIu/oR+scKQv/nxOrNA6hwNoojhQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782997697; c=relaxed/simple; bh=ytAugXMEonWRLI+JnF0MwPL1le2FpN2U9EIIp+gTq/M=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=tDnXi6nAVrV7CE4utWV0tFPzSfu8c3tled12gBAZA8c7/3eP1D1dzk6wYvEBLSQ4inzfVEOS7dDWjUKMuuOy6nSR10Mcx868njnGhQzpSQshtAecI5JjJzijYkZRdixA0mGH8aknSRex7I4bKiguIDpfnknEjf0AMDLKgAzoOjE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=UbKc3vag; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="UbKc3vag" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AD3131F000E9; Thu, 2 Jul 2026 13:08:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1782997696; bh=vzWg9+9+lN2dFJbszC3BynkSt9pozk4xm9GZgMWkChs=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=UbKc3vag5yX8mOZwvSjMikSf/b6uLBlN7UH9c9pEtmuH41D5ODuK1VwoTMu6Yt6JM hyu/EOJ7Bv/22wn9uaPmHP1H7kpsE7sBDsV11XKa5AMugH87OdweK8R3W41GBeeFJi mdMdW4QUIwWqstiRFQwhdCus6KRZOESPrI8Br3/2twFxzwdmSe/pCGOWsno4fRRXvI nf+1d2v2oPXE3PTwUrAM8CHsAu8JKnLeFH1rKkM4sluyA1vDj60FT2UBB9efKu5g8g MT2zTBl/b2hsi14kJI1e0n8to1UU6rwHWifbVmP8SVO4CmT0oRnyS9u+7slfXevYVf MaVyVaXYthN/w== Date: Thu, 2 Jul 2026 16:08:03 +0300 From: Mike Rapoport To: Lorenzo Stoakes Cc: Andrew Morton , Usama Arif , david@kernel.org, chrisl@kernel.org, kasong@tencent.com, ziy@nvidia.com, linux-mm@kvack.org, ying.huang@linux.alibaba.com, Baoquan He , 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" , ryan.roberts@arm.com, Vlastimil Babka , 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 Message-ID: References: <20260630164143.1595669-1-usama.arif@linux.dev> <20260630125024.6c079ea708630d99708e26f6@linux-foundation.org> <20260701164613.008aa13cb6187ec9597bf652@linux-foundation.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Thu, Jul 02, 2026 at 11:48:24AM +0100, Lorenzo Stoakes wrote: > +cc Mike re: CI. > > On Wed, Jul 01, 2026 at 04:46:13PM -0700, Andrew Morton wrote: > > On Wed, 1 Jul 2026 09:04:33 +0100 Lorenzo Stoakes wrote: > > > > > On Tue, Jun 30, 2026 at 12:50:24PM -0700, Andrew Morton wrote: > > > > On Tue, 30 Jun 2026 09:34:37 -0700 Usama Arif wrote: > > > > > > > > > This is the preparatory part of the PMD page table swapin work. > > > > > > > > Thanks. > > > > > > > > This comes reasonably reviewed, so I'll queue it in mm-new. > > > > > > > > Why? > > > > > > > > - Human review coverage and AI review make me believe this isn't the > > > > final version at all, but I do believe this is something we want in > > > > 7.2, and getting it under test early will help to push it along. > > > > > > > > - Getting it in there early means that others will base their work on > > > > material which will probably be upstreamed this cycle, so this gives > > > > them a more accurate base against which to work. > > > > > > > > Sashiko did find a lot to talk about, some of it pre-existing so can > > > > people who work on this code please take a look at > > > > > > > > https://sashiko.dev/#/patchset/20260630164143.1595669-1-usama.arif@linux.dev > > > > > > > > > > > > > > Hm, my understanding was that mm-new is where we take everything submitted for > > > early testing? > > > > > > Did something change? > > > > mm-new has always been a few day front-end to mm-unstable. To protect > > linux-next from brand new material. It serves no other purpose. > > Well it only serves a purpose if it gives us better testing. > > We have a CI running tests now though, Mike - is that predicated on material > being in mm-new or does it just grab the email? 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/ > If the CI is just grabbing email I wonder whether there's much purpose in the > mm-new branch at all. I can't say that CI I run has a great coverage. I don't know what coverage mm-new has though. > Thanks, Lorenzo -- Sincerely yours, Mike.