Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Ostapenko <igoreisberg@gmail.com>
To: linux-erofs@lists.ozlabs.org
Cc: Igor Eisberg <igoreisberg@gmail.com>
Subject: [PATCH] erofs-utils: fsck: fix issues related to --extract=X
Date: Fri, 28 Jan 2022 06:50:18 +0200	[thread overview]
Message-ID: <20220128045018.26-1-igoreisberg@gmail.com> (raw)
In-Reply-To: <YfNvloN0RAX0mHRn@B-P7TQMD6M-0146>

From: Igor Eisberg <igoreisberg@gmail.com>

Fix compile

Signed-off-by: Igor Ostapenko <igoreisberg@gmail.com>
---
 fsck/main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fsck/main.c b/fsck/main.c
index 2f13870..6f17d0e 100644
--- a/fsck/main.c
+++ b/fsck/main.c
@@ -196,7 +196,7 @@ static int erofsfsck_parse_options_cfg(int argc, char **argv)
 			return -EINVAL;
 		}
 		if (fsckcfg.preserve_owner || fsckcfg.preserve_perms ||
-			  fsckcfg.no_preserve_owner || fsckcfg.no_preserve_perms) {
+			  no_preserve_owner || no_preserve_perms) {
 			erofs_err("--[no-]preserve[-owner/-perms] must be used together with --extract=X");
 			return -EINVAL;
 		}
-- 
2.30.2


  parent reply	other threads:[~2022-01-28  4:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <YfC7rIs7%2FaAVdcS9@B-P7TQMD6M-0146.local>
2022-01-28  4:05 ` [PATCH] erofs-utils: fsck: fix issues related to --extract=X Igor Ostapenko
2022-01-28  4:22   ` Gao Xiang
2022-01-28  4:46     ` Igor Ostapenko
2022-01-28  4:50     ` Igor Ostapenko [this message]
2022-01-28  5:12       ` Gao Xiang
2022-01-28 16:00     ` Igor Ostapenko
2022-01-29  4:48       ` Gao Xiang
2022-01-21  0:31 Igor Ostapenko
2022-01-21  1:47 ` Gao Xiang
2022-01-26  3:10   ` Gao Xiang

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=20220128045018.26-1-igoreisberg@gmail.com \
    --to=igoreisberg@gmail.com \
    --cc=linux-erofs@lists.ozlabs.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