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 6C829346A10 for ; Thu, 2 Jul 2026 17:21:40 +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=1783012901; cv=none; b=c3FiKkbKMp0NexqqJB4CYpkrZsct061ATu07H+EV3KosadAjmqgdUGr7/g1RDXUhqWdI+ApJUBK3Tozyiddz1CeZoGeNr7N9/WPJYIJltP0yOBCDiSsxBQ4DWyEX2BVN8gmqW1MxW9PrAP90T0/96RBlR7lUp19wdeKSeazSFOc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783012901; c=relaxed/simple; bh=PlRXSRPV++bjN7bWwif730RnQ8rU04i0r0nfsWb3/TA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Rjq7dnnemevLJYivleX1/VV4XHSFxHafnFe49K3r+Pam7fdqciR1HfcQNQMOt7ZdZJYXDtE8Qd1sACBXL/ZMevMmJBMlkY7g/wsAZBgXyn+ZjFjEFyM3+JVj+T32a/A7ld81jwZU/DAYnC+WzKJZFJr4CspKnAC3L4ZsdU6iZ4Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=NPwAbT8H; 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="NPwAbT8H" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DFD651F00A3A; Thu, 2 Jul 2026 17:21:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783012900; bh=PlRXSRPV++bjN7bWwif730RnQ8rU04i0r0nfsWb3/TA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=NPwAbT8HDhhJwYXY33Dl0zR0tlK6KPp3Qf5+uvgeCZ/8QR857KCccgKaOsw4GhBAL 3SLy6MqIVdEj6QwkhLc6CobBgBjDkDXwm1ocfYUNx3foMA28fo7obk4hHYkbm03azV 7m+B4liqJnSwEOUa48JE2dMlyc/LUC9ifQQzjC++vpWqKHSEVp8fgk76rxsRm9Ys5D joaXOwXRy6K9wEUkejAbPvE2OacUKWvntj0AZLfoIuG1v28S2QnKRB+MxxYyREqWZ+ 9tMWhOCChJ647d0PZEu1HT8AIwx/dYnWAp6DfvCbB8qFhmEs75UCglJwyrhslIeA6L UGR0QPvOYCFoQ== Date: Thu, 2 Jul 2026 18:21:27 +0100 From: Lorenzo Stoakes To: "David Hildenbrand (Arm)" Cc: Mark Brown , Mike Rapoport , Andrew Morton , Usama Arif , 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> <756f3fb7-5129-435f-a84e-a2af48e323ab@kernel.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: <756f3fb7-5129-435f-a84e-a2af48e323ab@kernel.org> On Thu, Jul 02, 2026 at 07:10:34PM +0200, David Hildenbrand (Arm) wrote: > On 7/2/26 19:08, Lorenzo Stoakes wrote: > > On Thu, Jul 02, 2026 at 05:57:34PM +0100, Mark Brown wrote: > >> On Thu, Jul 02, 2026 at 05:53:48PM +0100, Lorenzo Stoakes wrote: > >> > >> > >>> 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? > >> > >> I currently test -next, mainline and stable plus my own stuff. > > > > Ack thanks! > > > > I guess in the long run then we can figure out a way to not necessarily even > > require mm-new at all, and instead let our CI try to handle as much as it can > > before -> linux-next :) > > > > As that'd be the nicest way and help reduce confusion about branches for > > mm-next. > > If we go the for-test route, we'd still have a branch where people/bots/tools > can do more elaborate tests when throwing stuff together. I still consider that > reasonable, but we'll have to see if we really need that. Ah fair point :) I mean we can have both of course! > > -- > Cheers, > > David Cheers, Lorenzo