From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 6/6] kernel/syscalls/open14: openat03: add new test-cases
Date: Thu, 28 Jan 2016 18:28:50 +0300 [thread overview]
Message-ID: <56AA33B2.6000600@oracle.com> (raw)
In-Reply-To: <20160128140109.GB16175@rei.lan>
Hi,
On 01/28/2016 05:01 PM, Cyril Hrubis wrote:
> Hi!
>> * create multiple directories and related temporary files;
>>
>> * create multiple directories and link files into them. Check
>> that files permissions correspond to the ones specified with
>> open()/openat().
> I would say that for newly added code it makes more sense to add new
> files in one patch. It's kind of strange to add more code to files you
> have added in previous one.
The previous patch was sent in the end of Dec, the last one quite recently.
I thought it would be easier to notice that the last one is included here
right now. Agree, it looks strange in the one patch set. Will squash it into
the previous.
Thanks,
Alexey
prev parent reply other threads:[~2016-01-28 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 12:28 [LTP] [PATCH v2 0/6] add open/openat + O_TMPFILE tests Alexey Kodanev
2016-01-28 12:28 ` [LTP] [PATCH v2 1/6] lib/tst_dir_is_empty: add a library function Alexey Kodanev
2016-01-28 12:28 ` [LTP] [PATCH v2 2/6] include/lapi/fcntl.h: add O_TMPFILE definition Alexey Kodanev
2016-01-28 12:28 ` [LTP] [PATCH v2 3/6] lib/safe_macros: add linkat() Alexey Kodanev
2016-01-28 12:28 ` [LTP] [PATCH v2 4/6] lib/safe_macros: add readlink() Alexey Kodanev
2016-01-28 12:28 ` [LTP] [PATCH v2 5/6] kernel/syscalls: add new test with 'open() + O_TMPFILE' Alexey Kodanev
2016-01-28 13:41 ` Cyril Hrubis
2016-01-28 12:28 ` [LTP] [PATCH v2 6/6] kernel/syscalls/open14: openat03: add new test-cases Alexey Kodanev
2016-01-28 14:01 ` Cyril Hrubis
2016-01-28 15:28 ` Alexey Kodanev [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=56AA33B2.6000600@oracle.com \
--to=alexey.kodanev@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