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 B042AC433EF for ; Mon, 13 Jun 2022 22:21:22 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229892AbiFMWVV (ORCPT ); Mon, 13 Jun 2022 18:21:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230240AbiFMWVU (ORCPT ); Mon, 13 Jun 2022 18:21:20 -0400 X-Greylist: delayed 574 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Mon, 13 Jun 2022 15:21:19 PDT Received: from nautica.notk.org (ipv6.notk.org [IPv6:2001:41d0:1:7a93::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D91F92DD5C for ; Mon, 13 Jun 2022 15:21:19 -0700 (PDT) Received: by nautica.notk.org (Postfix, from userid 108) id D6197C009; Tue, 14 Jun 2022 00:11:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codewreck.org; s=2; t=1655158302; bh=Ux/4hT39c14afeoew7+c9hXnBH4Wop2/T43c8QUzsXE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=3MtmjjnW/1Y+i6EFALMsGOv6GfF2dSqFOyZoeJvzGxVBIvRudwj8YIKRzJveL5GMu 2MAy7S+5LT9dNvm0JsDLy0iO5CANeWwe1wlnhuqR9/Gd++UEQTmj2znYka9o/BS/ca FbJsQIPh4aGwFjELvjZOm/pDVBHLktrC8GgQvfxQhGN2fT9PO5TY6RMJo1TBXavJlm 0docKaQFwaFt0b4KJx2yOWpEtENC6Bj+H9XL/tez/m1kcErCGO16xmor3nJlRW6+PS J0IOIRsX+RdgA482DF7/leFBggU79O8ywcTh3S0m5Fzz7BP+3EX6kYVMX2ZsZ8avhl ZucXbIv1ioS1Q== Received: from odin.codewreck.org (localhost [127.0.0.1]) by nautica.notk.org (Postfix) with ESMTPS id 8156BC009; Tue, 14 Jun 2022 00:11:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=codewreck.org; s=2; t=1655158302; bh=Ux/4hT39c14afeoew7+c9hXnBH4Wop2/T43c8QUzsXE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=3MtmjjnW/1Y+i6EFALMsGOv6GfF2dSqFOyZoeJvzGxVBIvRudwj8YIKRzJveL5GMu 2MAy7S+5LT9dNvm0JsDLy0iO5CANeWwe1wlnhuqR9/Gd++UEQTmj2znYka9o/BS/ca FbJsQIPh4aGwFjELvjZOm/pDVBHLktrC8GgQvfxQhGN2fT9PO5TY6RMJo1TBXavJlm 0docKaQFwaFt0b4KJx2yOWpEtENC6Bj+H9XL/tez/m1kcErCGO16xmor3nJlRW6+PS J0IOIRsX+RdgA482DF7/leFBggU79O8ywcTh3S0m5Fzz7BP+3EX6kYVMX2ZsZ8avhl ZucXbIv1ioS1Q== Received: from localhost (odin.codewreck.org [local]) by odin.codewreck.org (OpenSMTPD) with ESMTPA id 5e5af06f; Mon, 13 Jun 2022 22:11:36 +0000 (UTC) Date: Tue, 14 Jun 2022 07:11:21 +0900 From: Dominique Martinet To: Stephen Rothwell Cc: Linux Kernel Mailing List , Linux Next Mailing List Subject: Re: linux-next: bad commits in the v9fs tree Message-ID: References: <20220614075223.5c2ea764@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20220614075223.5c2ea764@canb.auug.org.au> Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org Stephen Rothwell wrote on Tue, Jun 14, 2022 at 07:52:23AM +1000: > 04608d78b66c ("Linux 5.19-rc1") > 9383b9134c66 ("fix the breakage in close_fd_get_file() calling conventions change") > > look like they were rebased or cherry-picked from Linus' tree.from > Linus' tree. From commits f2906aa86338 and 40a1926022d1 respectively. Ugh, thank you for noticing. I had an overly eager `rebase -i` that are usually noop and don't touch the top patches if left alone, but that only works if no merge is involved and that wasn't the case here -- I'll be more careful with my rebase root from now on so it hopefully won't happen again. Fixed my 9p-next branch so these two should be gone next time you update. Thanks, -- Dominique