All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 1/4] btrfs-progs: check/original: add the "0x" prefix for hex error number
Date: Tue,  4 May 2021 14:25:22 +0800	[thread overview]
Message-ID: <20210504062525.152540-2-wqu@suse.com> (raw)
In-Reply-To: <20210504062525.152540-1-wqu@suse.com>

In print_inode_error(), it print the error number in hex, but without
"0x" prefix.

Just add the prefix.

Signed-off-by: Qu Wenruo <wqu@suse.com>
---
 check/main.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/check/main.c b/check/main.c
index 0c4eb3ca5ded..1e65f8da4c6c 100644
--- a/check/main.c
+++ b/check/main.c
@@ -578,7 +578,7 @@ static void print_inode_error(struct btrfs_root *root, struct inode_record *rec)
 		root_objectid = root->root_key.offset;
 		fprintf(stderr, "reloc");
 	}
-	fprintf(stderr, "root %llu inode %llu errors %x",
+	fprintf(stderr, "root %llu inode %llu errors 0x%x",
 		(unsigned long long) root_objectid,
 		(unsigned long long) rec->ino, rec->errors);
 
-- 
2.31.1


  reply	other threads:[~2021-05-04  6:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04  6:25 [PATCH 0/4] btrfs-progs: check: add the ability to detect and report mixed inline and regular data extents Qu Wenruo
2021-05-04  6:25 ` Qu Wenruo [this message]
2021-05-04  6:25 ` [PATCH 2/4] btrfs-progs: check/original: " Qu Wenruo
2021-05-04  6:25 ` [PATCH 3/4] btrfs-progs: check/lowmem: detect and report mixed inline and regular extents properly Qu Wenruo
2021-05-04  6:25 ` [PATCH 4/4] btrfs-progs: fsck-tests: add test image for mixed inline and regular data extents Qu Wenruo
2021-05-04 13:30 ` [PATCH 0/4] btrfs-progs: check: add the ability to detect and report " Su Yue
2021-05-06 13:02 ` Qu Wenruo

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=20210504062525.152540-2-wqu@suse.com \
    --to=wqu@suse.com \
    --cc=linux-btrfs@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.