Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp433493pxu; Thu, 15 Oct 2020 07:36:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxC/aLxUsuvDo1oszdpnt0E2ydfWgTFt8D35HA28xjmLfn263mNwcZQwaE8WIM/tYJeVIx4 X-Received: by 2002:a17:907:2677:: with SMTP id ci23mr4714316ejc.270.1602772613476; Thu, 15 Oct 2020 07:36:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1602772613; cv=none; d=google.com; s=arc-20160816; b=MVhRpOBr0uFsk/sqMwsz+NAy9h8BN9pzwgiKhwy8sQnEw2bKOaw6DPv+VhkrJszMAI /mrj70zNLlbB02jo54sBaxxQ/vyXd/SQ+QYRb9/g2aWCS2PfCZQyR9qSpoB2FaVixreu raxGLOsKagsiQDcmNdxE6rl5BgZ7doCpMXlzTWl4vKNJa3K2Ih46sAximeZbZPJsdCOa BFUVYkyXLvM1IrhfPgsgygmiNwtkjA7PMr7ac6hKfy8Cf2G6+kpNliW7AoQWtZLLGFoo dq3S8NWU/BVxDtzL5hBV5ZxAXoH888Z0rdJYYfJgBVgTIH4I316DTcWR2+ybatEcN6AP 9NKQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:mail-followup-to:reply-to:message-id :subject:cc:to:from:date; bh=oNj/KbAmlerzkJtPLGP2btdoASpk7ZO05vwCOWyzozM=; b=SQrDBcH4XXEXlzVk8stxFTXugdlLuRnIffigqVLLlb9XJMa1xUEkYDI7RJcuOL1/1x Pxx8Or0ailOOHNZApwO0zRs291sgm7g4xMyDZYeGfB4fft0DB4h1Alx9ZAoIMiShfF3F A2aCB+epyMm7C4t/qTo8IODRMpM3cKWgnPU8Foo3M1HpdGr7GMeDgy+/mPBMa8qI4E8/ PE2w+2DeIAcvy6u72kKx97nTcJhwa+Xmj/GRwrpMnAIbbRXRd/Prk/Nh22+/qEVeu0JX fe76YL39KhFDeo6XfEf0jc4d1O8nOXaIZLWtm/favBlaEfkAllXeM5Zt/9oFhUQnDbii V3zg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a18si2206078edy.437.2020.10.15.07.36.22; Thu, 15 Oct 2020 07:36:53 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388534AbgJOOcv (ORCPT + 99 others); Thu, 15 Oct 2020 10:32:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:41758 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387861AbgJOOcu (ORCPT ); Thu, 15 Oct 2020 10:32:50 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id CBC8DAC24; Thu, 15 Oct 2020 14:32:48 +0000 (UTC) Received: by ds.suse.cz (Postfix, from userid 10065) id 9D5A5DA7C3; Thu, 15 Oct 2020 16:31:20 +0200 (CEST) Date: Thu, 15 Oct 2020 16:31:20 +0200 From: David Sterba To: Stephen Rothwell Cc: David Sterba , torvalds@linux-foundation.org, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] Btrfs updates for 5.10 Message-ID: <20201015143120.GO6756@twin.jikos.cz> Reply-To: dsterba@suse.cz Mail-Followup-To: dsterba@suse.cz, Stephen Rothwell , David Sterba , torvalds@linux-foundation.org, linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org References: <20201015114011.1f5f985a@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201015114011.1f5f985a@canb.auug.org.au> User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Thu, Oct 15, 2020 at 11:40:11AM +1100, Stephen Rothwell wrote: > Hi David, > On Mon, 12 Oct 2020 22:25:02 +0200 David Sterba wrote: > > > > Mishaps: > > > > - commit 62cf5391209a ("btrfs: move btrfs_rm_dev_replace_free_srcdev > > outside of all locks") is a rebase leftover after the patch got > > merged to 5.9-rc8 as a466c85edc6f ("btrfs: move > > btrfs_rm_dev_replace_free_srcdev outside of all locks"), the > > remaining part is trivial and the patch is in the middle of the > > series so I'm keeping it there instead of rebasing > > And yet, this entire pull request has been rebased since what was in > linux-next on Tuesday (and what would still be there today except I > dropped it because of several conflicts) ... it looks like it was > rebased a week ago, but then never included in your "for-next" branch. > So I supposed it has had your internal testing, at least. I was on vacation last week and rebased the to-be-pulled branch on top of v5.9-rc8 so there are at least a few days before the pull request is sent. The patch queue was feature frozen for 2 weeks, there should be no surprises whether it's rc7 or rc8, but the latter contained a corruption fix so it was desirable to rebase the development queue. Due to my limited time I forgot to update the for-next branches, sorry. We do enough internal testing of course.