public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/3] f2fs: clean up w/ dotdot_name
Date: Thu, 30 Nov 2023 18:30:28 +0000	[thread overview]
Message-ID: <170136902865.21709.4443581224551288791.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231116062556.2451839-1-chao@kernel.org>

Hello:

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

On Thu, 16 Nov 2023 14:25:54 +0800 you wrote:
> Just cleanup, no logic changes.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
>  fs/f2fs/namei.c | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)

Here is the summary with links:
  - [f2fs-dev,1/3] f2fs: clean up w/ dotdot_name
    https://git.kernel.org/jaegeuk/f2fs/c/ff6584ac2c4b
  - [f2fs-dev,2/3] f2fs: use shared inode lock during f2fs_fiemap()
    https://git.kernel.org/jaegeuk/f2fs/c/9458915036dd
  - [f2fs-dev,3/3] f2fs: fix to check return value of f2fs_reserve_new_block()
    https://git.kernel.org/jaegeuk/f2fs/c/956fa1ddc132

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



      parent reply	other threads:[~2023-11-30 18:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  6:25 [PATCH 1/3] f2fs: clean up w/ dotdot_name Chao Yu
2023-11-16  6:25 ` [PATCH 2/3] f2fs: use shared inode lock during f2fs_fiemap() Chao Yu
2023-11-16  6:25 ` [PATCH 3/3] f2fs: fix to check return value of f2fs_reserve_new_block() Chao Yu
2023-11-30 18:30 ` patchwork-bot+f2fs [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=170136902865.21709.4443581224551288791.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox