All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Qi Han <hanqi@vivo.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove unnessary comment in __may_age_extent_tree
Date: Mon, 24 Apr 2023 18:10:19 +0000	[thread overview]
Message-ID: <168235981938.17900.13599013308884334410.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230418060954.67585-1-hanqi@vivo.com>

Hello:

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

On Tue, 18 Apr 2023 14:09:54 +0800 you wrote:
> This comment make no sense and is in the wrong place, so let's
> remove it.
> 
> Signed-off-by: Qi Han <hanqi@vivo.com>
> ---
>  fs/f2fs/extent_cache.c | 1 -
>  1 file changed, 1 deletion(-)

Here is the summary with links:
  - [f2fs-dev] f2fs: remove unnessary comment in __may_age_extent_tree
    https://git.kernel.org/jaegeuk/f2fs/c/8375be2b6414

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




_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Qi Han <hanqi@vivo.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove unnessary comment in __may_age_extent_tree
Date: Mon, 24 Apr 2023 18:10:19 +0000	[thread overview]
Message-ID: <168235981938.17900.13599013308884334410.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230418060954.67585-1-hanqi@vivo.com>

Hello:

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

On Tue, 18 Apr 2023 14:09:54 +0800 you wrote:
> This comment make no sense and is in the wrong place, so let's
> remove it.
> 
> Signed-off-by: Qi Han <hanqi@vivo.com>
> ---
>  fs/f2fs/extent_cache.c | 1 -
>  1 file changed, 1 deletion(-)

Here is the summary with links:
  - [f2fs-dev] f2fs: remove unnessary comment in __may_age_extent_tree
    https://git.kernel.org/jaegeuk/f2fs/c/8375be2b6414

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-04-24 18:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  6:09 [f2fs-dev] [PATCH] f2fs: remove unnessary comment in __may_age_extent_tree Qi Han via Linux-f2fs-devel
2023-04-18  6:09 ` Qi Han
2023-04-21  2:27 ` [f2fs-dev] " Chao Yu
2023-04-21  2:27   ` Chao Yu
2023-04-21 19:20   ` [f2fs-dev] " Jaegeuk Kim
2023-04-21 19:20     ` Jaegeuk Kim
2023-04-22 12:15     ` [f2fs-dev] " Chao Yu
2023-04-22 12:15       ` Chao Yu
2023-04-21  6:51 ` [f2fs-dev] [PATCH] f2fs: move wrong comment to right place " Qi Han via Linux-f2fs-devel
2023-04-21  6:51   ` Qi Han
2023-04-24 18:10 ` patchwork-bot+f2fs [this message]
2023-04-24 18:10   ` [f2fs-dev] [PATCH] f2fs: remove unnessary comment " patchwork-bot+f2fs

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=168235981938.17900.13599013308884334410.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+f2fs@kernel.org \
    --cc=hanqi@vivo.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.