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 6D2023C0A1B for ; Tue, 26 May 2026 19:09:14 +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=1779822555; cv=none; b=NjUWLDYwLEINupcSpgsrLxFu2uekRuW1xuuoHy6FhqwG6PgNy+0/J39jULwVoVV4OJSodQIYLmWSxl8sfvnNOhmMwKiyhg/ne0veuDqlPphFlxPQ76JbbRtZlsZ5mjo9M1+k+v1E8GnafkjmrViI/Rdu4NrrlTIAT/AXkkCC1QI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779822555; c=relaxed/simple; bh=2X2dkD2WnTvcYvw8q2Bi5bHO7ajZQzLmVd8m+KkMbos=; h=Date:From:To:Cc:Subject:Message-Id:In-Reply-To:References: Mime-Version:Content-Type; b=TxmjrW0ikLpAcJk/hIpKNZIndNK67NwCZIerViNBXVBouweb7p0Of4hYwkweywMnG9uRPHJQP6FtlQEQGqUzXAOaLTxz/gBvfws8oJsPvys2x6SDEs+4IpY5tJ9XFKq+vP6/85xCv+qRq8pCrjwpwEV+r54pX3XfvYdSWLIPNHs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=GNr35sdM; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="GNr35sdM" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8A2441F00A3A; Tue, 26 May 2026 19:09:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=korg; t=1779822553; bh=1Q+7F9jkpzpdArbUFuaX2fYSOOw55N51m56qOke4nGA=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=GNr35sdMl8L0pN7iIvRepKjYtv/5tv0fDmU1kyIXm4XoTDCjiW0oVsLh+U/pbn40a eZiZcZ4kEozF+jGgwN1JryENR26NyBhp7PnNo7CcK8AhAOUERG5q0kI9VtXyP0dqwp wUqL6k4RqU19aNN1SzcMbQpmmDcr+qC9EKICQ/rw= Date: Tue, 26 May 2026 12:09:13 -0700 From: Andrew Morton To: Lorenzo Stoakes Cc: "David Hildenbrand (Arm)" , Nico Pache , "Vlastimil Babka (SUSE)" , linux-kernel@vger.kernel.org, linux-mm@kvack.org, liam@infradead.org, mhocko@suse.com, rppt@kernel.org, vbabka@suse.cz, willy@infradead.org Subject: Re: Process (was Re: [PATCH mm-hotfixes-unstable v18 00/14] khugepaged: add mTHP) collapse support Message-Id: <20260526120913.937a4d483af214ad050166dc@linux-foundation.org> In-Reply-To: References: <20260522150009.121603-1-npache@redhat.com> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) 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=UTF-8 Content-Transfer-Encoding: 8bit On Tue, 26 May 2026 09:33:08 +0100 Lorenzo Stoakes wrote: > [trimmed cc list to avoid noise, apologies if I excluded anybody who is > interested in this!] > > On Fri, May 22, 2026 at 11:13:42PM +0200, David Hildenbrand (Arm) wrote: > > On 5/22/26 18:11, Nico Pache wrote: > > > On Fri, May 22, 2026 at 9:13 AM Vlastimil Babka (SUSE) > > > wrote: > > >> > > >> On 5/22/26 17:07, Nico Pache wrote: > > >>> > > >>> Whoops I manually changed the coverletter subject to reflect that this > > >>> in on mm-hotfixes-unstable but never updated the others... > > >> > > >> But why? That branch is for hotfixes that would go to the current 7.1-rcX > > >> series. mm-unstable would be the correct one for this, AFAICT. > > > > > > Sorry this was a misunderstanding. The goal here was to base this off > > > the closest base commit behind where my v17 already lies in the tree. > > > > Ah, I guess this is a problem of "v17 is already in mm-unstable, so against what > > to base v18". > > > > Yeah, we touched on that problem in the LSF/MM process discussion ... > > I may be misremembering but... :) [correct me if wrong]: > > Wasn't the general conclusion that we maintain a stable branch (Linus's tree + > stuff that's been reviewed and is locked in for next release), and have people > base work against that? That was the plan when I initially set up the mm.git branches. It turned out to be quite impractical because it takes so long to get material into mm-stable worthiness: around -rc4/-rc5. We could address that by delaying everything by four weeks - so MM's window is out of phase with Linus's. So there's a lot of "stable" material in mm.git when Linus is at -rc1/-rc2. Problem with this is that by -rc5/-rc6 we'll have a large amount of material queued up for the next -rc cycle and it is against linux-next rules to add this to -next. And until it's had decent -next exposure we can't declare it "stable". This needs a diagram ;)