public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Su Yue <suy.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH v2] fstests: btrfs/006: Fix false alert due to output change
Date: Tue, 3 Jan 2017 12:07:19 +0800	[thread overview]
Message-ID: <20170103040719.GI1859@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170103031617.439-1-suy.fnst@cn.fujitsu.com>

On Mon, Jan 02, 2017 at 10:16:17PM -0500, Su Yue wrote:
> Btrfs-progs v4.9 changed "device status" output by adding one more
> space, which differs from golden output.
> Fix it by using filter '_filter_spaces' to convert multi space into one.

You missed your SOB line. I added

Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>

and applied the patch.

Thanks,
Eryu

      reply	other threads:[~2017-01-03  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03  3:16 [PATCH v2] fstests: btrfs/006: Fix false alert due to output change Su Yue
2017-01-03  4:07 ` Eryu Guan [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=20170103040719.GI1859@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=suy.fnst@cn.fujitsu.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