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 A18D9C64ED9 for ; Tue, 21 Feb 2023 07:20:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233563AbjBUHUO (ORCPT ); Tue, 21 Feb 2023 02:20:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233557AbjBUHUM (ORCPT ); Tue, 21 Feb 2023 02:20:12 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E2E38A5DA for ; Mon, 20 Feb 2023 23:19:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1676963965; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=DkIg+wanBd11Z/7UnnKjYFa+oSlHGs/qlgwPU2NatOs=; b=VWDWv1kBm7YLGpUg9UlUM1cKR6Hp3yaZ2nsvHFl/cpzSb17ZuCp0IgeNAT/JkUvObTxsYr 9rj7+DotlmciOH8CT7AdCgbw2O2KQIcAhjWpBznPOr1UM1m1NTXeBl5L79UrhUPmkxAy7f Z8Z6ondoxZ4A0eqZTDJmiYIX3p3o1Hc= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-91-hys1ylktOw-SM318ZO8Oyg-1; Tue, 21 Feb 2023 02:19:20 -0500 X-MC-Unique: hys1ylktOw-SM318ZO8Oyg-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id C29B4101A5BA; Tue, 21 Feb 2023 07:19:19 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id 6EACE492B05; Tue, 21 Feb 2023 07:19:18 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20230221174401.7198357d@canb.auug.org.au> References: <20230221174401.7198357d@canb.auug.org.au> <20230220152933.1ab8fa4a@canb.auug.org.au> <20230220190157.3b43b9a7@canb.auug.org.au> To: Stephen Rothwell Cc: dhowells@redhat.com, Matthew Wilcox , Andrew Morton , Steve French , CIFS , Linux Kernel Mailing List , Linux Next Mailing List , Steve French , "Vishal Moola (Oracle)" Subject: Re: linux-next: manual merge of the mm-stable tree with the cifs tree MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2351090.1676963957.1@warthog.procyon.org.uk> Date: Tue, 21 Feb 2023 07:19:17 +0000 Message-ID: <2351091.1676963957@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.9 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stephen Rothwell wrote: > in the cifs tree introduces a new usage of it in code that is used in > the cifs code ... so someone has to figure out what the merge > resolution is between the 2 trees (how to replace that new usage) and > let me know and then we need to test that combination for a while > before asking Linus to take it. It seems I can't fix my patch and give Steve a replacement patch because the new filemap_get_folios_tag() that I would need to use hasn't been added upstream yet. Do we have any idea when the mm tree might land? David