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 5476D23EAAD for ; Thu, 2 Jul 2026 16:54:01 +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=1783011242; cv=none; b=YlGUQFNrpEUN9cIYGTeUU++jT5msXcvL2t8kcDAORTCzZL6F7VjdU4jTTFTMi9irv31GcGlsqmrh7bAAcwYdlPiqzwWskqlr86JIBF7LYPLhO+3QC/rTUj2NXC+yU9TIRSoo0nwJyQi2fA3/wEZWgvEcRd4g9qmHKHoYskEpH58= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783011242; c=relaxed/simple; bh=k6EVF8D67PWMBOraEeULqOwUnWbU4qO0ejs4bTRJycc=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=M3SNS9hL6UBMKtU4TNm7Z2qTP8qnY8wcyq7RZd0EstC1YZ35o409mcic3Vxu/lJUlOZNurc0zKp+lrZf46QyNDGz7Z2JXoCeMFSm+UON7iAD1/Ek5kFWIxforLBNMwnNG2IFO/xm6RpifTjWzkhBy8jaMcDjN+hl11HfZJ4+kdk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=GWosjpEC; 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="GWosjpEC" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0DAFC1F00A3A; Thu, 2 Jul 2026 16:53:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783011241; bh=MGNWDJlk6DwODfpBNfvuIjdfDz4b4TnwObejyBQmtwU=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=GWosjpECJhOR/x2RdqukgEQ2EpEXIeCNjRKWZYAy5aXRnJkiDuCSvDA9iyxpYkFpt WRD5z+f0i1+QGoIu9CXX7rG9Sdos/2XbPwAvyWExEOncrMtq59GhhKUD4QWwDNQa5B +NPIbOWyz9wjwqOl3Owcx4VlLA4TrzBECaCHSiOB3zn5aeu5xg2jsyyyU2KvbDIFqr DAV9W8tVL+fWp0xuQzEeFgndNqW0mg8MyUX1fKGJJNiDT6IHfTpLNUKOQrn62u+Vro MX9zz8Vb+L7JsJE/3g1QMYyVQZWuTKuASCkqYPgpRgi1ovEaIUCHtUKpasSumpp39c fwfzuVRlhQRRw== Date: Thu, 2 Jul 2026 17:53:48 +0100 From: Lorenzo Stoakes To: Mike Rapoport 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, Mark Brown 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: +cc Mark On Thu, Jul 02, 2026 at 04:08:03PM +0300, Mike Rapoport wrote: > 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: ... > > > > 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 Well we're very grateful for what coverage it has :) and that's nice to have it work with email like that also, makes life simpler. Mark - are you running tests based on mm-new? I'm not sure where things stand on that? > > > Thanks, Lorenzo > > -- > Sincerely yours, > Mike. Thanks, Lorenzo