From: Filipe Manana <fdmanana@gmail.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: fstests@vger.kernel.org,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] fstest: btrfs: remove _need_to_be_root fix btrfs/118
Date: Thu, 24 Mar 2016 11:08:56 +0000 [thread overview]
Message-ID: <CAL3q7H5APJE6bWpi=kYMuC4sMRvYuEh5ouVTLxfQCRQO4EThew@mail.gmail.com> (raw)
In-Reply-To: <1458814439-6418-1-git-send-email-anand.jain@oracle.com>
On Thu, Mar 24, 2016 at 10:13 AM, Anand Jain <anand.jain@oracle.com> wrote:
> commit 56ff01f471c9b72de0a447b37cdb1051adcede6a
> xfstests: remove _need_to_be_root
>
> Removed _need_to_be_root(), and so btrfs/118 needs an update
https://git.kernel.org/cgit/fs/xfs/xfstests-dev.git/commit/?id=3a9242688d64c669ca764ee2c5599abfc885c131
It's always a good idea to check if one is using the latest git branch
and the mailing list... :)
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> tests/btrfs/118 | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tests/btrfs/118 b/tests/btrfs/118
> index 3ed1cbef1068..740cb92b0669 100755
> --- a/tests/btrfs/118
> +++ b/tests/btrfs/118
> @@ -45,7 +45,6 @@ _cleanup()
> . ./common/dmflakey
>
> # real QA test starts here
> -_need_to_be_root
> _supported_fs btrfs
> _supported_os Linux
> _require_scratch
> --
> 2.7.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2016-03-24 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 10:13 [PATCH] fstest: btrfs: remove _need_to_be_root fix btrfs/118 Anand Jain
2016-03-24 11:07 ` Eryu Guan
2016-03-24 11:08 ` Filipe Manana [this message]
2016-03-24 11:27 ` Anand Jain
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='CAL3q7H5APJE6bWpi=kYMuC4sMRvYuEh5ouVTLxfQCRQO4EThew@mail.gmail.com' \
--to=fdmanana@gmail.com \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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 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).