From: Chao Yu <chao@kernel.org>
To: Daniel Rosenberg <drosen@google.com>,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH] dump.f2fs: Add help description for -rfyPo
Date: Wed, 19 Jun 2024 09:30:01 +0800 [thread overview]
Message-ID: <f36fe619-da24-4b8f-ae3c-75064658e264@kernel.org> (raw)
In-Reply-To: <20240619012509.1885974-1-drosen@google.com>
On 2024/6/19 9:25, Daniel Rosenberg wrote:
> These were described in man pages, but not within the help message.
>
> Signed-off-by: Daniel Rosenberg <drosen@google.com>
Can you please check below patch?
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git/commit/?h=dev-test&id=c07b0954506a159f68358edddc09be0a4d810e61
Thanks,
> ---
> fsck/main.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/fsck/main.c b/fsck/main.c
> index 6edc902..901fa7a 100644
> --- a/fsck/main.c
> +++ b/fsck/main.c
> @@ -97,6 +97,11 @@ void dump_usage()
> MSG(0, " -S sparse_mode\n");
> MSG(0, " -a [SSA dump segno from #1~#2 (decimal), for all 0~-1]\n");
> MSG(0, " -b blk_addr (in 4KB)\n");
> + MSG(0, " -r Recursively dump from the root inode\n");
> + MSG(0, " -f Do not prompt before dumping\n");
> + MSG(0, " -y Alias for -f\n");
> + MSG(0, " -P Preserve mode/Owner/Group for dumped inode\n");
> + MSG(0, " -o <path> Dump inodes to the given path\n");
> MSG(0, " -V print the version number and exit\n");
>
> exit(1);
>
> base-commit: c1a97862b05d8a736ad8719939395c61bd71c982
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2024-06-19 1:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 1:25 [f2fs-dev] [PATCH] dump.f2fs: Add help description for -rfyPo Daniel Rosenberg via Linux-f2fs-devel
2024-06-19 1:30 ` Chao Yu [this message]
2024-06-19 1:37 ` Daniel Rosenberg via Linux-f2fs-devel
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=f36fe619-da24-4b8f-ae3c-75064658e264@kernel.org \
--to=chao@kernel.org \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).