From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 1/2] syscalls/access02: reconstruct and convert to new API
Date: Mon, 25 Jul 2016 15:19:12 +0200 [thread overview]
Message-ID: <20160725131912.GB12533@rei> (raw)
In-Reply-To: <1469011479-808-1-git-send-email-fenggw-fnst@cn.fujitsu.com>
Hi!
I've added missing SAFE_CLOSE() to the R_OK and W_OK cases in the
access_test() since otherwise the test will fail on large enough -i
since it will use all awailable file descriptors.
Both patches pushed, thanks.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2016-07-25 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 8:08 [LTP] [PATCH] syscalls/access02: reconstruct and convert to new API Guangwen Feng
2016-07-19 11:49 ` Cyril Hrubis
2016-07-20 10:44 ` [LTP] [PATCH v2 1/2] " Guangwen Feng
2016-07-25 13:19 ` 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=20160725131912.GB12533@rei \
--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