All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Hsu <robinhsu@google.com>
To: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
	chao@kernel.org
Cc: linux-kernel@vger.kernel.org, Robin Hsu <robinhsu@google.com>
Subject: [PATCH 0/1] f2fs-tools:fsck.f2fs Fix bad return value
Date: Mon, 26 Oct 2020 17:39:05 +0800	[thread overview]
Message-ID: <20201026093905.1498859-1-robinhsu@google.com> (raw)

f2fs-tools:fsck.f2fs: Fix always return 1 (error) after asking user to restore
           lost files into ./lost_found

Robin Hsu (1):
  f2fs-toos:fsck.f2fs Fix bad return value

 fsck/fsck.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

-- 
2.29.0.rc2.309.g374f81d7ae-goog


WARNING: multiple messages have this Message-ID (diff)
From: Robin Hsu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
	 chao@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [f2fs-dev] [PATCH 0/1] f2fs-tools:fsck.f2fs Fix bad return value
Date: Mon, 26 Oct 2020 17:39:05 +0800	[thread overview]
Message-ID: <20201026093905.1498859-1-robinhsu@google.com> (raw)

f2fs-tools:fsck.f2fs: Fix always return 1 (error) after asking user to restore
           lost files into ./lost_found

Robin Hsu (1):
  f2fs-toos:fsck.f2fs Fix bad return value

 fsck/fsck.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

-- 
2.29.0.rc2.309.g374f81d7ae-goog



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

             reply	other threads:[~2020-10-26  9:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26  9:39 Robin Hsu [this message]
2020-10-26  9:39 ` [f2fs-dev] [PATCH 0/1] f2fs-tools:fsck.f2fs Fix bad return value Robin Hsu 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=20201026093905.1498859-1-robinhsu@google.com \
    --to=robinhsu@google.com \
    --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.