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 667E3C05027 for ; Mon, 20 Feb 2023 14:30:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232056AbjBTOak (ORCPT ); Mon, 20 Feb 2023 09:30:40 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52768 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232017AbjBTOai (ORCPT ); Mon, 20 Feb 2023 09:30:38 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6CD7411EA2 for ; Mon, 20 Feb 2023 06:29:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1676903390; 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=x5p6lK28Ra573v7+UHzSn0UqRqk59msus4yoHKjo37Y=; b=Jt0UNBnHGCzm+L0RHqWxYpFD41YEs3W9hip31AxTf8nLgxEAAptoWRZtIx+ApYWrphCDti 4Uu6wBVJsv0cmWFjFZKzO2x5Y3dL0w3jGmTPVHlOqB7K3PUJAgOBph3xJVEAYtcCyW21JU PsK0sG0XYcYDf5axjqNlszHrYAWPlMs= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-74-BUWw3wZaOMeCm6RwB8xb4Q-1; Mon, 20 Feb 2023 09:29:44 -0500 X-MC-Unique: BUWw3wZaOMeCm6RwB8xb4Q-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id DF90329AB44F; Mon, 20 Feb 2023 14:29:43 +0000 (UTC) Received: from warthog.procyon.org.uk (unknown [10.33.36.18]) by smtp.corp.redhat.com (Postfix) with ESMTP id 702734097544; Mon, 20 Feb 2023 14:29:42 +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: References: <20230220152933.1ab8fa4a@canb.auug.org.au> To: Matthew Wilcox Cc: dhowells@redhat.com, Stephen Rothwell , 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: <1676389.1676903381.1@warthog.procyon.org.uk> Date: Mon, 20 Feb 2023 14:29:41 +0000 Message-ID: <1676391.1676903381@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.1 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Matthew Wilcox wrote: > Doesn't look too bad to me. Dave's commit is just removing the > functions, so it doesn't matter how they're being changed. > > The real question in my mind is why for-next is being updated two days > before the merge window with new patches. What's the point in -next > if patches are being added at this late point? It's more of a transfer of a subset of my iov/splice patches from the linux-block tree to the cifs tree. I thought Jens would've dropped my branch from his tree for the moment. David