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 D7F8DC77B73 for ; Mon, 24 Apr 2023 18:10:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232280AbjDXSK3 (ORCPT ); Mon, 24 Apr 2023 14:10:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49300 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231985AbjDXSKV (ORCPT ); Mon, 24 Apr 2023 14:10:21 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B18A2729A for ; Mon, 24 Apr 2023 11:10:20 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 42DB8627F2 for ; Mon, 24 Apr 2023 18:10:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPS id 8F018C4339B; Mon, 24 Apr 2023 18:10:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1682359819; bh=ZIggbnNo61Pd9qiJAbI89ZQyfggHn/sva6khpCzkQds=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=nXW528/0qimThez3goOdL5VgfN04J5lJyzvXfzD/aPHw84FDgxojF+1NeW0EpDput 22NE+bxebHPpbO8ZgfTKckVQT1CpNTLv6ZOomu5RT2oOK9CaufIgox15fWNF8TIy+a qHoqSlPdZym8Pi0d26F4ilYZZNdho7ZQvc9GW56ak4OwWhyH5ttwPg74bS2u2Mo3Ce B8Mtcgo4gW7wwujjL6GGvPgzT6e6HS4nIKySbS3epkWgWacSQvfiYxjbtYsT1fcCQJ ija41oYhDD4NVZJoLvLdXKIBuhCzRjdNakLlovNJlDaj/2EWkFtW2Vt79//sIPrbFw fzbq0eLnScHow== Received: from aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (localhost.localdomain [127.0.0.1]) by aws-us-west-2-korg-oddjob-1.ci.codeaurora.org (Postfix) with ESMTP id 6B09CC395D8; Mon, 24 Apr 2023 18:10:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate node blocks for atomic write block replacement From: patchwork-bot+f2fs@kernel.org Message-Id: <168235981943.17900.16631584887911592592.git-patchwork-notify@kernel.org> Date: Mon, 24 Apr 2023 18:10:19 +0000 References: <20230424154440.23279-1-daeho43@gmail.com> In-Reply-To: <20230424154440.23279-1-daeho43@gmail.com> To: Daeho Jeong Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com, daehojeong@google.com Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello: This patch was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Mon, 24 Apr 2023 08:44:40 -0700 you wrote: > From: Daeho Jeong > > When a node block is missing for atomic write block replacement, we need > to allocate it in advance of the replacement. > > Fixes: 3db1de0e582c ("f2fs: change the current atomic write way") > Signed-off-by: Daeho Jeong > > [...] Here is the summary with links: - [f2fs-dev] f2fs: allocate node blocks for atomic write block replacement https://git.kernel.org/jaegeuk/f2fs/c/994b442b66a4 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html