Received-SPF: pass (google.com: domain of linux-kernel+bounces-91087-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to check return value
 __allocate_new_segment
From: patchwork-bot+f2fs@kernel.org
Message-Id: 
 <170957642885.16816.17706378772269565327.git-patchwork-notify@kernel.org>
Date: Mon, 04 Mar 2024 18:20:28 +0000
References: <1709281555-11373-1-git-send-email-zhiguo.niu@unisoc.com>
In-Reply-To: <1709281555-11373-1-git-send-email-zhiguo.niu@unisoc.com>
To: Zhiguo Niu <zhiguo.niu@unisoc.com>
Cc: jaegeuk@kernel.org, chao@kernel.org, ke.wang@unisoc.com,
 linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
 hongyu.jin@unisoc.com

Hello:

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

On Fri, 1 Mar 2024 16:25:54 +0800 you wrote:
> __allocate_new_segment may return error when get_new_segment
> fails, so its caller should check its return value.
> 
> Signed-off-by: Zhiguo Niu <zhiguo.niu@unisoc.com>
> ---
>  fs/f2fs/f2fs.h     | 2 +-
>  fs/f2fs/recovery.c | 2 +-
>  fs/f2fs/segment.c  | 7 +++++--
>  3 files changed, 7 insertions(+), 4 deletions(-)

Here is the summary with links:
  - [f2fs-dev,1/2] f2fs: fix to check return value __allocate_new_segment
    https://git.kernel.org/jaegeuk/f2fs/c/28f66cc65403
  - [f2fs-dev,2/2] f2fs: fix to check return value of f2fs_gc_range
    https://git.kernel.org/jaegeuk/f2fs/c/22af1b8c31cb

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