All of lore.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] f2fs: support .shutdown in f2fs_sops
Date: Sun, 14 Apr 2024 15:32:45 +0000	[thread overview]
Message-ID: <171310876526.3156.6732886911990694550.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240229143838.45149-1-chao@kernel.org>

Hello:

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

On Thu, 29 Feb 2024 22:38:38 +0800 you wrote:
> Support .shutdown callback in f2fs_sops, then, it can be called to
> shut down the file system when underlying block device is marked dead.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
>  fs/f2fs/f2fs.h  |  2 ++
>  fs/f2fs/file.c  | 70 ++++++++++++++++++++++++++++++-------------------
>  fs/f2fs/super.c |  6 +++++
>  3 files changed, 51 insertions(+), 27 deletions(-)

Here is the summary with links:
  - [f2fs-dev] f2fs: support .shutdown in f2fs_sops
    https://git.kernel.org/jaegeuk/f2fs/c/ee745e4736fb

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



WARNING: multiple messages have this Message-ID (diff)
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] f2fs: support .shutdown in f2fs_sops
Date: Sun, 14 Apr 2024 15:32:45 +0000	[thread overview]
Message-ID: <171310876526.3156.6732886911990694550.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240229143838.45149-1-chao@kernel.org>

Hello:

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

On Thu, 29 Feb 2024 22:38:38 +0800 you wrote:
> Support .shutdown callback in f2fs_sops, then, it can be called to
> shut down the file system when underlying block device is marked dead.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
>  fs/f2fs/f2fs.h  |  2 ++
>  fs/f2fs/file.c  | 70 ++++++++++++++++++++++++++++++-------------------
>  fs/f2fs/super.c |  6 +++++
>  3 files changed, 51 insertions(+), 27 deletions(-)

Here is the summary with links:
  - [f2fs-dev] f2fs: support .shutdown in f2fs_sops
    https://git.kernel.org/jaegeuk/f2fs/c/ee745e4736fb

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

  parent reply	other threads:[~2024-04-14 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 14:38 [PATCH] f2fs: support .shutdown in f2fs_sops Chao Yu
2024-02-29 14:38 ` [f2fs-dev] " Chao Yu
2024-03-12  1:42 ` Chao Yu
2024-03-12  1:42   ` [f2fs-dev] " Chao Yu
2024-03-13  1:33   ` Jaegeuk Kim
2024-03-13  1:33     ` [f2fs-dev] " Jaegeuk Kim
2024-04-14 15:32 ` patchwork-bot+f2fs [this message]
2024-04-14 15:32   ` 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=171310876526.3156.6732886911990694550.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 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.