From: Bill O'Donnell <billodo@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tests/xfs/040: document purpose
Date: Mon, 18 Dec 2017 08:47:32 -0600 [thread overview]
Message-ID: <20171218144732.GA11237@redhat.com> (raw)
In-Reply-To: <20171215204118.17740-1-mcgrof@kernel.org>
On Fri, Dec 15, 2017 at 12:41:18PM -0800, Luis R. Rodriguez wrote:
> Getting xfs/040 to "pass" takes a bit of effort, however the effort
> to require updating xfsprogs is purely an xfsprogs maintainer task
> only. There no functional gain by users of xfs or a QA team to get
> this test to pass. This is not trivial from the current description
> so document this.
>
> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
Looks good...
Reviewed-by: Bill O'Donnell <billodo@redhat.com>
> ---
> tests/xfs/040 | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/tests/xfs/040 b/tests/xfs/040
> index fadb888cbfaf..a0abc42f3720 100755
> --- a/tests/xfs/040
> +++ b/tests/xfs/040
> @@ -3,6 +3,11 @@
> #
> # compare-libxfs test
> #
> +# The purpose of this test is only to nag the maintainer of xfsprogs to try to
> +# keep xfsprogs's libxfs files in sync with the latest kernel's libxfs. There
> +# is no functional need for anyone to actually run this test to confirm
> +# proper XFS functionalilty, this is an xfsprogs maintainer test.
> +#
> #-----------------------------------------------------------------------
> # Copyright (c) 2000-2001 Silicon Graphics, Inc. All Rights Reserved.
> #
> --
> 2.15.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-12-18 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 20:41 [PATCH] tests/xfs/040: document purpose Luis R. Rodriguez
2017-12-18 14:47 ` Bill O'Donnell [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=20171218144732.GA11237@redhat.com \
--to=billodo@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox