linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: fix installation for extended output files
Date: Thu, 1 Jun 2017 12:07:33 +0800	[thread overview]
Message-ID: <20170601040733.GW23805@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1496286073-23298-1-git-send-email-yangx.jy@cn.fujitsu.com>

On Thu, Jun 01, 2017 at 11:01:13AM +0800, Xiao Yang wrote:
> The installation of these extended output files are skipped
> because they aren't matched by xfstests.  So we rename them
> to adapt building rules.
> 
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>

This patch is 2.4M in size, no wonder it didn't hit the list..

(cc linux-xfs list for these xfs specific tests)

> ---
>  tests/xfs/018                         |    8 +-
>  tests/xfs/018.op.irix                 | 5628 ---------------------------------
>  tests/xfs/018.op.linux                | 4714 ---------------------------
>  tests/xfs/018.out.irix                | 5628 +++++++++++++++++++++++++++++++++
>  tests/xfs/018.out.linux               | 4714 +++++++++++++++++++++++++++
>  tests/xfs/018.out.trans_buf           | 1821 +++++++++++
>  tests/xfs/018.out.trans_inode         | 2609 +++++++++++++++
>  tests/xfs/018.trans_buf               | 1821 -----------
>  tests/xfs/018.trans_inode             | 2609 ---------------

xfs/018 081 and 082 are all marked as 'deprecated', I'm wondering if we
can just remove them.

>  tests/xfs/040                         |    4 +-
>  tests/xfs/040.good                    |   16 -
>  tests/xfs/040.out.good                |   16 +

xfs/040 is doing source code diff between userspace vs kernel space, I'm
not sure if this is still needed. But xfs/040 requires KWORKAREA points
to a directory that contains both userspace and kernel code, I suspect
it's rarely run.

>  tests/xfs/081                         |    2 +-
>  tests/xfs/081.out.ugquota.trans_inode | 3091 ++++++++++++++++++
>  tests/xfs/081.ugquota.trans_inode     | 3091 ------------------
>  tests/xfs/082                         |    8 +-
>  tests/xfs/082.op.irix                 | 5628 ---------------------------------
>  tests/xfs/082.op.linux                | 4714 ---------------------------
>  tests/xfs/082.out.irix                | 5628 +++++++++++++++++++++++++++++++++
>  tests/xfs/082.out.linux               | 4714 +++++++++++++++++++++++++++
>  tests/xfs/082.out.trans_buf           | 1821 +++++++++++
>  tests/xfs/082.out.trans_inode         | 2609 +++++++++++++++
>  tests/xfs/082.trans_buf               | 1821 -----------
>  tests/xfs/082.trans_inode             | 2609 ---------------
>  24 files changed, 32662 insertions(+), 32662 deletions(-)

Thanks,
Eryu

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170601025327.GU23805@eguan.usersys.redhat.com>
     [not found] ` <1496286073-23298-1-git-send-email-yangx.jy@cn.fujitsu.com>
2017-06-01  4:07   ` Eryu Guan [this message]
2017-06-01 15:48     ` [PATCH 2/2] xfs: fix installation for extended output files Darrick J. Wong
2017-06-02  2:40       ` Xiao Yang
2017-06-02  5:45         ` Darrick J. Wong
2017-06-02  6:24           ` Eryu Guan

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=20170601040733.GW23805@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=yangx.jy@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;
as well as URLs for NNTP newsgroup(s).