All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Sheng Yong <shengyong@oppo.com>, jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/4] dump.f2fs: remove unavailable optiont -g
Date: Mon, 14 Nov 2022 15:10:26 +0800	[thread overview]
Message-ID: <a002bbd4-7946-2bc6-b101-182acac0e4b5@kernel.org> (raw)
In-Reply-To: <20221110140723.92752-1-shengyong@oppo.com>

On 2022/11/10 22:07, Sheng Yong wrote:
> Option "-g" for dump.f2fs is unavailable and not used in dump.f2fs.
> 
> Signed-off-by: Sheng Yong <shengyong@oppo.com>

Reviewed-by: Chao Yu <chao@kernel.org>

Thanks,


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

      parent reply	other threads:[~2022-11-14  7:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 14:07 [f2fs-dev] [PATCH 1/4] dump.f2fs: remove unavailable optiont -g Sheng Yong via Linux-f2fs-devel
2022-11-10 14:07 ` [f2fs-dev] [PATCH 2/4] fsck.f2fs: add parentheses for SB_MASK Sheng Yong via Linux-f2fs-devel
2022-11-14  7:10   ` Chao Yu
2022-11-10 14:07 ` [f2fs-dev] [PATCH 3/4] fsck.f2fs: fix potential overflow of copying i_name Sheng Yong via Linux-f2fs-devel
2022-11-14  7:14   ` Chao Yu
2022-11-10 14:07 ` [f2fs-dev] [PATCH 4/4] fsck.f2fs: avoid uncessary recalculation Sheng Yong via Linux-f2fs-devel
2022-11-14  7:29   ` Chao Yu
2022-11-14 14:17     ` [f2fs-dev] [PATCH v2] " Sheng Yong via Linux-f2fs-devel
2022-11-14 14:59       ` Chao Yu
2022-11-14  7:10 ` Chao Yu [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=a002bbd4-7946-2bc6-b101-182acac0e4b5@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=shengyong@oppo.com \
    /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.