All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 1/5] btrfs-progs: tune: add the missing newline for --convert-from-block-group-tree
Date: Wed,  3 Apr 2024 08:37:36 +1030	[thread overview]
Message-ID: <39cc5f46367eec2769ab2dc45c38e350001dfa0f.1712095635.git.wqu@suse.com> (raw)
In-Reply-To: <cover.1712095635.git.wqu@suse.com>

There is a missing newline for a successful
--convert-from-block-group-tree run, meanwhile
--convert-to-block-group-tree has the correct newline.

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

diff --git a/tune/convert-bgt.c b/tune/convert-bgt.c
index dd3a8c750604..1263b147241e 100644
--- a/tune/convert-bgt.c
+++ b/tune/convert-bgt.c
@@ -270,7 +270,7 @@ iterate_bgs:
 		return ret;
 	}
 	pr_verbose(LOG_DEFAULT,
-		"Converted filesystem with block-group-tree to extent tree feature");
+		"Converted filesystem with block-group-tree to extent tree feature\n");
 	return 0;
 
 error:
-- 
2.44.0


  reply	other threads:[~2024-04-02 22:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 22:07 [PATCH v2 0/5] btrfs-progs: zoned devices support for bgt feature Qu Wenruo
2024-04-02 22:07 ` Qu Wenruo [this message]
2024-04-02 22:07 ` [PATCH v2 2/5] btrfs-progs: mkfs: use proper zoned compatible write " Qu Wenruo
2024-04-02 22:07 ` [PATCH v2 3/5] btrfs-progs: tune: properly open zoned devices for RW Qu Wenruo
2024-04-02 22:07 ` [PATCH v2 4/5] btrfs-progs: tests-mkfs: add test case for zoned block group tree feature Qu Wenruo
2024-04-02 22:07 ` [PATCH v2 5/5] btrfs-progs: tests-misc: add a test case to check zoned bgt conversion Qu Wenruo
2024-04-03 13:50 ` [PATCH v2 0/5] btrfs-progs: zoned devices support for bgt feature David Sterba

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=39cc5f46367eec2769ab2dc45c38e350001dfa0f.1712095635.git.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.