From: "Theodore Ts'o" <tytso@mit.edu>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Eric Biggers <ebiggers@google.com>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] xfstests-bld: add f2fs support
Date: Fri, 18 Nov 2016 17:07:40 -0500 [thread overview]
Message-ID: <20161118220740.pisri5zaldj7h5ic@thunk.org> (raw)
In-Reply-To: <20161118180421.GA31226@jaegeuk>
On Fri, Nov 18, 2016 at 10:04:21AM -0800, Jaegeuk Kim wrote:
>
> I realize that xfstests-bld is really great to test multiple kernel versions.
> I guess it can be quite doable to test arm-based kernel as well, as I can see
> cross compile environment.
I have had reports that some folks have run into problems using the
armhf chroot on an Android device. I'm not sure what problems they
ran into, since their report was quite vague. I'm aware of one
namespace-related test that will fail when you run xfstests in a
chroot, and I would expect that SELinux would have to be disabled, but
other than that I would have expected it to work.
If you (or anyone else) have managed to use the armhf chroot
successfully on an Android device, please let me know, and let me know
if there are any updates we can make to Documentation/android-xfstests.md.
Unfortunately I haven't had time to investigate those reports myself.
If someone has time to try it out and send me a more detailed report,
that would be great.
Thanks!!
- Ted
next prev parent reply other threads:[~2016-11-18 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 19:52 [PATCH] xfstests-bld: add f2fs support Eric Biggers
2016-11-18 4:38 ` Jaegeuk Kim
2016-11-18 4:51 ` Theodore Ts'o
2016-11-18 5:11 ` Jaegeuk Kim
2016-11-18 16:22 ` Theodore Ts'o
2016-11-18 18:04 ` Jaegeuk Kim
2016-11-18 22:07 ` Theodore Ts'o [this message]
2016-12-08 3:22 ` Theodore Ts'o
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=20161118220740.pisri5zaldj7h5ic@thunk.org \
--to=tytso@mit.edu \
--cc=ebiggers@google.com \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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