All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
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: control nat_bits feature via mount option
Date: Tue, 11 Mar 2025 03:30:32 +0000	[thread overview]
Message-ID: <174166383201.3785903.5420256276801883297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250308051846.29079-1-chao@kernel.org>

Hello:

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

On Sat,  8 Mar 2025 13:18:46 +0800 you wrote:
> Introduce a new mount option "nat_bits" to control nat_bits feature,
> by default nat_bits feature is disabled.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
>  Documentation/filesystems/f2fs.rst |  2 ++
>  fs/f2fs/f2fs.h                     |  1 +
>  fs/f2fs/node.c                     |  3 +++
>  fs/f2fs/super.c                    | 15 +++++++++++++++
>  4 files changed, 21 insertions(+)

Here is the summary with links:
  - [f2fs-dev] f2fs: control nat_bits feature via mount option
    https://git.kernel.org/jaegeuk/f2fs/c/c2ecba026586

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: 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: control nat_bits feature via mount option
Date: Tue, 11 Mar 2025 03:30:32 +0000	[thread overview]
Message-ID: <174166383201.3785903.5420256276801883297.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250308051846.29079-1-chao@kernel.org>

Hello:

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

On Sat,  8 Mar 2025 13:18:46 +0800 you wrote:
> Introduce a new mount option "nat_bits" to control nat_bits feature,
> by default nat_bits feature is disabled.
> 
> Signed-off-by: Chao Yu <chao@kernel.org>
> ---
>  Documentation/filesystems/f2fs.rst |  2 ++
>  fs/f2fs/f2fs.h                     |  1 +
>  fs/f2fs/node.c                     |  3 +++
>  fs/f2fs/super.c                    | 15 +++++++++++++++
>  4 files changed, 21 insertions(+)

Here is the summary with links:
  - [f2fs-dev] f2fs: control nat_bits feature via mount option
    https://git.kernel.org/jaegeuk/f2fs/c/c2ecba026586

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



  reply	other threads:[~2025-03-11  3:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-08  5:18 [f2fs-dev] [PATCH] f2fs: control nat_bits feature via mount option Chao Yu via Linux-f2fs-devel
2025-03-08  5:18 ` Chao Yu
2025-03-11  3:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-03-11  3:30   ` [f2fs-dev] " 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=174166383201.3785903.5420256276801883297.git-patchwork-notify@kernel.org \
    --to=linux-f2fs-devel@lists.sourceforge.net \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patchwork-bot+f2fs@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.