From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] syscalls/pipe01: Cleanup && convert to new API.
Date: Tue, 17 May 2016 13:44:04 +0200 [thread overview]
Message-ID: <20160517114404.GA12051@rei.lan> (raw)
In-Reply-To: <1463037494-7284-1-git-send-email-yangx.jy@cn.fujitsu.com>
Hi!
I've cleaned up the test even more and pushed, thanks.
The test does not need temporary directory, the SAFE_* macros cannot
fail, etc..
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2016-05-17 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 7:18 [LTP] [PATCH 1/2] syscalls/pipe01: Cleanup && convert to new API Xiao Yang
2016-05-12 7:18 ` [LTP] [PATCH 2/2] syscalls/fanotify*: Cleanup && fix compiler warnings Xiao Yang
2016-05-17 12:11 ` Cyril Hrubis
2016-05-18 0:51 ` Xiao Yang
2016-06-16 2:30 ` [LTP] [PATCH v2] syscalls/fanotify*: Cleanup Xiao Yang
2016-09-22 14:27 ` Cyril Hrubis
2016-05-17 11:44 ` Cyril Hrubis [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=20160517114404.GA12051@rei.lan \
--to=chrubis@suse.cz \
--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