From: chrubis@suse.cz
To: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] syscall's error vaule and flag tests
Date: Thu, 20 Mar 2014 17:22:43 +0100 [thread overview]
Message-ID: <20140320162242.GA5013@rei.Home> (raw)
In-Reply-To: <1393914721-5288-1-git-send-email-wangxg.fnst@cn.fujitsu.com>
Hi!
> Currently I send many patches about syscall's error value and flag tests.
> I think it has made some disorder in mail list, sorry. I will put these
> similar patches in one thread to keep some orderliness, thanks.
As far as I can figure out which patches should be reviewed it's fine,
just make sure to number the versions so that I can figure out which one
is the latest.
And if I forget to look at some of your patches feel free to ping me.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-03-20 16:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 6:31 [LTP] syscall's error vaule and flag tests Xiaoguang Wang
2014-03-04 6:31 ` [LTP] [PATCH 1/4] fcntl/fcntl31.c: add I/O availability signals test for fcntl(2) Xiaoguang Wang
2014-03-04 6:31 ` [LTP] [PATCH 2/4] mincore/mincore01.c: cleanup Xiaoguang Wang
2014-03-04 6:32 ` [LTP] [PATCH 3/4] mknodat/mknodat02.c: add ELOOP and EROFS error value test Xiaoguang Wang
2014-03-20 18:45 ` chrubis
2014-03-04 6:32 ` [LTP] [PATCH 4/4] msync/msync03.c: add EBUSY test for msync(2) Xiaoguang Wang
2014-03-20 16:22 ` 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=20140320162242.GA5013@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