From: chrubis@suse.cz
To: "Wang, Xiaoguang" <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] access(2): add ELOOP, ENOTDIR, EROFS error number test
Date: Wed, 23 Oct 2013 16:35:36 +0200 [thread overview]
Message-ID: <20131023143536.GA25390@rei.Home> (raw)
In-Reply-To: <52662BFB.9050105@cn.fujitsu.com>
Hi!
> access/access05.c: add ELOOP, ENOTDIR error number test
>
> new access/access06.c: add EROFS error number test
Sorry for not being clear enough the first time. When I said adding the
testcases to access05 I meant all of them including the EROFS (contrary
to my first thoughts). (I can fix this myself if you want). Otherwise
the code is fine.
Also looking at increased demand for EROFS tests, I'm trying to figure
out more general LTP lib API for creating and mounting the readonly
image, so that the code pattern is not repeated all over. But for now
let's go with the manual approach and I will convert all usages once the
new API is in place.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-10-23 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 7:40 [LTP] [PATCH] access(2): add ELOOP, ENOTDIR, EROFS error number test Wang, Xiaoguang
2013-10-23 14:35 ` chrubis [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=20131023143536.GA25390@rei.Home \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=wangxg.fnst@cn.fujitsu.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