From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chunhai Guo <guochunhai@vivo.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v6] f2fs: add reserved nodes for privileged users
Date: Fri, 15 Aug 2025 16:40:19 +0000 [thread overview]
Message-ID: <175527601949.1161945.7999749862771332410.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250807133501.551848-1-guochunhai@vivo.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 7 Aug 2025 21:35:01 +0800 you wrote:
> This patch allows privileged users to reserve nodes via the
> 'reserve_node' mount option, which is similar to the existing
> 'reserve_root' option.
>
> "-o reserve_node=<N>" means <N> nodes are reserved for privileged
> users only.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v6] f2fs: add reserved nodes for privileged users
https://git.kernel.org/jaegeuk/f2fs/c/a3b0697610ba
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
prev parent reply other threads:[~2025-08-15 16:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 13:35 [f2fs-dev] [PATCH v6] f2fs: add reserved nodes for privileged users Chunhai Guo via Linux-f2fs-devel
2025-08-07 22:57 ` Jaegeuk Kim via Linux-f2fs-devel
2025-08-08 0:54 ` Chao Yu via Linux-f2fs-devel
2025-08-08 11:34 ` Chunhai Guo via Linux-f2fs-devel
2025-08-08 11:34 ` Chunhai Guo via Linux-f2fs-devel
2025-08-13 3:25 ` Chunhai Guo via Linux-f2fs-devel
2025-08-13 2:11 ` Chao Yu via Linux-f2fs-devel
2025-08-15 16:40 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=175527601949.1161945.7999749862771332410.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=guochunhai@vivo.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).