Received-SPF: pass (google.com: domain of linux-kernel+bounces-91-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [f2fs-dev] [PATCH 1/4] f2fs: allocate new section if it's not new
From: patchwork-bot+f2fs@kernel.org
Message-Id: 
 <170258703206.30587.6882657417862323311.git-patchwork-notify@kernel.org>
Date: Thu, 14 Dec 2023 20:50:32 +0000
References: <20231204180428.925779-1-jaegeuk@kernel.org>
In-Reply-To: <20231204180428.925779-1-jaegeuk@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon,  4 Dec 2023 10:04:25 -0800 you wrote:
> If fsck can allocate a new zone, it'd be better to use that instead of
> allocating a new one.
> 
> And, it modifies kernel messages.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/4] f2fs: allocate new section if it's not new
    https://git.kernel.org/jaegeuk/f2fs/c/15a76c8014f9
  - [f2fs-dev,2/4] f2fs: fix write pointers on zoned device after roll forward
    https://git.kernel.org/jaegeuk/f2fs/c/9dad4d964291
  - [f2fs-dev,3/4] f2fs: check write pointers when checkpoint=disable
    https://git.kernel.org/jaegeuk/f2fs/c/aca90eea8a90
  - [f2fs-dev,4/4] f2fs: let's finish or reset zones all the time
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html