All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Naohiro Aota <Naohiro.Aota@wdc.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] fstests: add missing checks of fallocate feature
Date: Wed, 3 Mar 2021 08:04:53 +0000	[thread overview]
Message-ID: <PH0PR04MB7416904201518476C2FF13609B989@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210303060152.r2xi46ke6bpfifyk@naota-xeon

On 03/03/2021 07:02, Naohiro Aota wrote:
> On Tue, Mar 02, 2021 at 06:13:04PM +0900, Johannes Thumshirn wrote:
>> From: Naohiro Aota <naohiro.aota@wdc.com>
>>
>> Many test cases use xfs_io -c 'falloc' but forgot to add
>> _require_xfs_io_command "falloc". This will fail the test case if we run
>> the test case on a file system without fallcoate support e.g. F2FS ZZ
>>
> 
> The sentences between "This will " .. "e.g. F2FS ZZ" should be removed.
> # Vim command leaked to the log ... oops.
> 

Ok will fix that up

  reply	other threads:[~2021-03-04  0:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  9:13 [PATCH 0/2] fstests: two preperation patches for zoned device support Johannes Thumshirn
2021-03-02  9:13 ` [PATCH 1/2] fstests: add missing checks of fallocate feature Johannes Thumshirn
2021-03-02 19:00   ` Josef Bacik
2021-03-03  6:01   ` Naohiro Aota
2021-03-03  8:04     ` Johannes Thumshirn [this message]
2021-03-02  9:13 ` [PATCH 2/2] btrfs: require discard functionality from scratch device Johannes Thumshirn
2021-03-02 19:01   ` Josef Bacik
2021-03-03  5:58 ` [PATCH 0/2] fstests: two preperation patches for zoned device support Naohiro Aota
2021-03-03  8:04   ` Johannes Thumshirn

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=PH0PR04MB7416904201518476C2FF13609B989@PH0PR04MB7416.namprd04.prod.outlook.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@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.