From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DFF9DC433F5 for ; Sat, 19 Feb 2022 07:28:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241647AbiBSH2T (ORCPT ); Sat, 19 Feb 2022 02:28:19 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:36824 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229737AbiBSH2S (ORCPT ); Sat, 19 Feb 2022 02:28:18 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D481675605; Fri, 18 Feb 2022 23:27:59 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 8062D68BEB; Sat, 19 Feb 2022 08:27:55 +0100 (CET) Date: Sat, 19 Feb 2022 08:27:55 +0100 From: Christoph Hellwig To: Matthew Wilcox Cc: Stephen Rothwell , Andrew Morton , Linux Kernel Mailing List , Linux Next Mailing List , linux-mm@kvack.org, William Kucharski , Mike Rapoport , Alistair Popple , Alex Sierra , Christoph Hellwig , Hugh Dickins Subject: Re: linux-next: manual merge of the akpm-current tree with the folio tree Message-ID: <20220219072755.GA27008@lst.de> References: <20220215180043.23879691@canb.auug.org.au> <20220216172109.72fd0a38@canb.auug.org.au> <20220217163026.5e48ccb1@canb.auug.org.au> <20220216215124.169c42a52e31575cedc4dea5@linux-foundation.org> <20220217173810.0addd3ed@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Thu, Feb 17, 2022 at 09:19:43PM +0000, Matthew Wilcox wrote: > > > Let's try Matthew's idea - I'll get Hugh's and Christoph's series via > > > linux-next and shall figure out the rest. > > > > OK, but I am on vacation from tomorrow until Feb 28th, so I will assume > > you will have it all ready for me by then. > > I assume you mean that you'll do one last pull and release a > next-20220218, rather than saying that the next release will be > next-20220229? > > I have pushed out f82e2137bc1e to infradead/for-next. xfstests currently > running. It includes: Not sure where this mail started, but I already suggested a git tree in the cover letter of the ZONE_DEVICE series, so the overall approach sounds fine to me.