From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/3] btrfs-progs: misc-tests: add test to ensure the restored image can be mounted
Date: Sat, 17 Apr 2021 08:18:11 +0800 [thread overview]
Message-ID: <31b7aadb-70bf-6498-2be5-6f74fe978d0f@gmx.com> (raw)
In-Reply-To: <20210416174629.GH7604@twin.jikos.cz>
On 2021/4/17 上午1:46, David Sterba wrote:
> On Fri, Mar 26, 2021 at 08:50:47PM +0800, Qu Wenruo wrote:
>> This new test case is to make sure the restored image file has been
>> properly enlarged so that newer kernel won't complain.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>> ---
>> .../047-image-restore-mount/test.sh | 19 +++++++++++++++++++
>> 1 file changed, 19 insertions(+)
>> create mode 100755 tests/misc-tests/047-image-restore-mount/test.sh
>>
>> diff --git a/tests/misc-tests/047-image-restore-mount/test.sh b/tests/misc-tests/047-image-restore-mount/test.sh
>> new file mode 100755
>> index 000000000000..7f12afa2bab6
>> --- /dev/null
>> +++ b/tests/misc-tests/047-image-restore-mount/test.sh
>> @@ -0,0 +1,19 @@
>> +#!/bin/bash
>> +# Verify that the restored image of an empty btrfs can still be mounted
> ^^^^^
>
> I've seen that in patches and comments, the use of word 'btrfs' instead
> of 'filesystem' sounds a bit inappropriate to me, so I change it
> whenever I see it. It's perhaps matter of taste and style, one can write
> it also as 'btrfs filesystem' but that may belong to some more polished
> documentation, so you can go with just 'filesystem'.
>
Thanks for pointing this out.
I'll use 'filesystem' from now on.
Thanks,
Qu
prev parent reply other threads:[~2021-04-17 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 12:50 [PATCH 0/3] btrfs-progs: image: make restored image file to be properly enlarged Qu Wenruo
2021-03-26 12:50 ` [PATCH 1/3] btrfs: image: remove the dead stat() call Qu Wenruo
2021-03-26 14:08 ` Su Yue
2021-03-26 12:50 ` [PATCH 2/3] btrfs-progs: image: enlarge the output file if no tree modification is needed for restore Qu Wenruo
2021-03-26 13:52 ` Su Yue
2021-03-26 14:29 ` Su Yue
2021-04-16 17:40 ` David Sterba
2021-04-17 0:17 ` Qu Wenruo
2021-03-26 12:50 ` [PATCH 3/3] btrfs-progs: misc-tests: add test to ensure the restored image can be mounted Qu Wenruo
2021-04-16 17:46 ` David Sterba
2021-04-17 0:18 ` Qu Wenruo [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=31b7aadb-70bf-6498-2be5-6f74fe978d0f@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox