From: Eric Sandeen <sandeen@redhat.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] xfstests: Test xfs_fsr / swapext management of di_forkoff w/ selinux
Date: Fri, 18 Oct 2013 12:27:26 -0500 [thread overview]
Message-ID: <52616F7E.7040003@redhat.com> (raw)
In-Reply-To: <20131018172635.GE11404@dhcp-13-216.nay.redhat.com>
On 10/18/13 12:26 PM, Eryu Guan wrote:
...
> There's trailing whitespaces issue here, otherwise looks good to me.
>
> I suppose the seq number can be fixed at commit time, as well as the
> trailing whitespaces.
>
> Reviewed-by: Eryu Guan <eguan@redhat.com>
>
> Thanks!
> Eryu
>
> BTW, test fails on 3.12-rc5 kernel
Yup. (actually it's a userspace bug)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-18 17:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 4:16 [PATCH] xfstests: Test xfs_fsr / swapext management of di_forkoff w/ selinux Eric Sandeen
2013-10-18 4:48 ` Eryu Guan
2013-10-18 5:04 ` Eric Sandeen
2013-10-18 16:23 ` [PATCH V2] " Eric Sandeen
2013-10-18 17:26 ` Eryu Guan
2013-10-18 17:27 ` Eric Sandeen [this message]
2013-10-22 21:03 ` Rich Johnston
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=52616F7E.7040003@redhat.com \
--to=sandeen@redhat.com \
--cc=guaneryu@gmail.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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