From: Shuang Qiu <shuang.qiu@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/removexattr02:skip the test if no xattr support
Date: Fri, 24 Jun 2016 21:20:32 +0800 [thread overview]
Message-ID: <576D33A0.7090607@oracle.com> (raw)
In-Reply-To: <1959236773.1678649.1466772016581.JavaMail.zimbra@redhat.com>
On 06/24/2016 08:40 PM, Jan Stancek wrote:
>
>
>
> ----- Original Message -----
>> From: "shuang qiu" <shuang.qiu@oracle.com>
>> To: ltp@lists.linux.it
>> Sent: Friday, 24 June, 2016 5:36:02 AM
>> Subject: [LTP] [PATCH] syscalls/removexattr02:skip the test if no xattr support
>>
>> From: Shuang Qiu <shuang.qiu@oracle.com>
>>
>> Return TCONF if there is no xattr support in fs or mount without user_xattr
>> option
> Why only in removexattr02? Should we do the same for removexattr01?
removexattr01 already handle such situation.
Thanks
Shuang
>
> Regards,
> Jan
next prev parent reply other threads:[~2016-06-24 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 3:36 [LTP] [PATCH] syscalls/removexattr02:skip the test if no xattr support shuang.qiu
2016-06-24 12:40 ` Jan Stancek
2016-06-24 13:20 ` Shuang Qiu [this message]
2016-06-24 13:25 ` Jan Stancek
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=576D33A0.7090607@oracle.com \
--to=shuang.qiu@oracle.com \
--cc=ltp@lists.linux.it \
/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