From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] mkfs.gfs2: fix tests call to gfs_max_blocks
Date: Fri, 4 May 2018 11:22:02 +0100 [thread overview]
Message-ID: <14a770b3-48c3-9aff-f946-12385cfe8301@redhat.com> (raw)
In-Reply-To: <20180504100056.10953-1-Valentin.Vidic@CARNet.hr>
On 04/05/18 11:00, Valentin Vidic wrote:
> Replace call to nonexisting util_max_blocks.
>
> Signed-off-by: Valentin Vidic <Valentin.Vidic@CARNet.hr>
> ---
> tests/mkfs.at | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
Applied - thanks!
Andy
> diff --git a/tests/mkfs.at b/tests/mkfs.at
> index 7ae6fcc2..ee444f50 100644
> --- a/tests/mkfs.at
> +++ b/tests/mkfs.at
> @@ -52,7 +52,7 @@ AT_CLEANUP
>
> AT_SETUP([Max. blocks, max. block size])
> AT_KEYWORDS(mkfs.gfs2 mkfs)
> -GFS_FSCK_CHECK([$GFS_MKFS -p lock_nolock -b 4096 $GFS_TGT $(util_max_blocks 4096)])
> +GFS_FSCK_CHECK([$GFS_MKFS -p lock_nolock -b 4096 $GFS_TGT $(gfs_max_blocks 4096)])
> AT_CLEANUP
>
> AT_SETUP([Max. resource group size])
>
prev parent reply other threads:[~2018-05-04 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 10:00 [Cluster-devel] [PATCH] mkfs.gfs2: fix tests call to gfs_max_blocks Valentin Vidic
2018-05-04 10:22 ` Andrew Price [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=14a770b3-48c3-9aff-f946-12385cfe8301@redhat.com \
--to=anprice@redhat.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).