From: Nikolay Borisov <nborisov@suse.com>
To: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
Cc: dsterba@suse.com, linux-btrfs@vger.kernel.org,
Marcos Paulo de Souza <mpdesouza@suse.com>
Subject: Re: [PATCH 1/2] btrfs-progs: mkfs-tests: Set $csum so mkfs.btrfs does not fail
Date: Tue, 10 Dec 2019 10:33:57 +0200 [thread overview]
Message-ID: <5220654e-4f9c-70f0-1f28-6555a48cd46b@suse.com> (raw)
In-Reply-To: <20191205153647.31961-1-marcos.souza.org@gmail.com>
On 5.12.19 г. 17:36 ч., Marcos Paulo de Souza wrote:
> From: Marcos Paulo de Souza <mpdesouza@suse.com>
>
> Signed-off-by: Marcos Paulo de Souza <mpdesouza@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
> ---
> tests/mkfs-tests/020-basic-checksums-mount/test.sh | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/mkfs-tests/020-basic-checksums-mount/test.sh b/tests/mkfs-tests/020-basic-checksums-mount/test.sh
> index 41ef5417..b7252786 100755
> --- a/tests/mkfs-tests/020-basic-checksums-mount/test.sh
> +++ b/tests/mkfs-tests/020-basic-checksums-mount/test.sh
> @@ -12,6 +12,7 @@ prepare_test_dev
>
> test_mkfs_mount_checksum()
> {
> + csum=$1
> run_check_stdout $SUDO_HELPER "$TOP/mkfs.btrfs" -f --csum "$csum" "$TEST_DEV" | grep -q "Checksum:.*$csum"
> run_check $SUDO_HELPER "$TOP/btrfs" inspect-internal dump-super "$TEST_DEV"
> run_check $SUDO_HELPER "$TOP/btrfs" check "$TEST_DEV"
>
prev parent reply other threads:[~2019-12-10 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 15:36 [PATCH 1/2] btrfs-progs: mkfs-tests: Set $csum so mkfs.btrfs does not fail Marcos Paulo de Souza
2019-12-05 15:36 ` [PATCH 2/2] btrfs-progs: mkfs-tests: Change $dev1 to TEST_DEV Marcos Paulo de Souza
2019-12-10 8:34 ` Nikolay Borisov
2019-12-10 8:33 ` Nikolay Borisov [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=5220654e-4f9c-70f0-1f28-6555a48cd46b@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcos.souza.org@gmail.com \
--cc=mpdesouza@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;
as well as URLs for NNTP newsgroup(s).