public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: Eric Sandeen <sandeen@sandeen.net>,
	Yi Zhang <yi.zhang@redhat.com>,
	"logang@deltatee.com" <logang@deltatee.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests] common/xfs: ignore the 32M log size during mkfs.xfs
Date: Fri, 21 Oct 2022 23:56:57 +0000	[thread overview]
Message-ID: <20221021235656.fxl7k4x3zjbbaiul@shindev> (raw)
In-Reply-To: <0f2957e1-2b05-73ec-85b1-91cb643ccb54@nvidia.com>

On Oct 21, 2022 / 21:42, Chaitanya Kulkarni wrote:

...

> I think creating a minimal setup is a part of the testcase and we should 
> not change it, unless there is a explicit reason for doing so.

I see, I find no reason to change the "minimal log size policy". Let's go with
64MB log size to keep it.

Yi, would you mind reposting v2 with size=64m?

-- 
Shin'ichiro Kawasaki

  reply	other threads:[~2022-10-21 23:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19  5:12 [PATCH blktests] common/xfs: ignore the 32M log size during mkfs.xfs Yi Zhang
2022-10-19  6:06 ` Chaitanya Kulkarni
2022-10-19  6:16 ` Chaitanya Kulkarni
2022-10-19 14:19   ` Eric Sandeen
2022-10-19 19:18     ` Chaitanya Kulkarni
2022-10-21  8:58       ` Shinichiro Kawasaki
2022-10-21 21:42         ` Chaitanya Kulkarni
2022-10-21 23:56           ` Shinichiro Kawasaki [this message]
2022-10-23 15:27             ` Yi Zhang
2022-10-24  0:50               ` Shinichiro Kawasaki
2022-10-24  6:32                 ` Yi Zhang
2022-10-24 10:31                   ` Shinichiro Kawasaki
2022-10-25  0:42                 ` Chaitanya Kulkarni
2022-10-25  1:53                   ` Shinichiro Kawasaki

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=20221021235656.fxl7k4x3zjbbaiul@shindev \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=chaitanyak@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=sandeen@sandeen.net \
    --cc=yi.zhang@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