From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 3/4] syscalls/fanotify14: new test to validate FAN_REPORT_FID interface return values
Date: Fri, 19 Apr 2019 18:38:38 +1000 [thread overview]
Message-ID: <20190419083836.GB15974@lithium.mbobrowski.org> (raw)
In-Reply-To: <20190416140434.GB20437@rei>
On Tue, Apr 16, 2019 at 04:04:34PM +0200, Cyril Hrubis wrote:
> Hi!
> This one is missing runtest entry as well, otherwise looks fine.
Simple oversight. I've updated the commit accordingly. I will post through a
new patch series with all the fixes shortly.
--
Matthew Bobrowski
next prev parent reply other threads:[~2019-04-19 8:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 10:01 [LTP] [PATCH 0/4] fanotify: FAN_REPORT_FID and Directory Modification Events Matthew Bobrowski
2019-04-02 10:01 ` [LTP] [PATCH 1/4] syscalls/fanotify01: add FAN_REPORT_FID test cases Amir Goldstein
2019-04-15 15:18 ` Cyril Hrubis
2019-04-02 10:02 ` [LTP] [PATCH 2/4] syscalls/fanotify13: new test to verify FAN_REPORT_FID functionality Matthew Bobrowski
2019-04-16 13:41 ` Cyril Hrubis
2019-04-16 14:23 ` Amir Goldstein
2019-04-19 8:37 ` Matthew Bobrowski
2019-04-19 9:07 ` Amir Goldstein
2019-04-02 10:02 ` [LTP] [PATCH 3/4] syscalls/fanotify14: new test to validate FAN_REPORT_FID interface return values Matthew Bobrowski
2019-04-16 14:04 ` Cyril Hrubis
2019-04-19 8:38 ` Matthew Bobrowski [this message]
2019-04-02 10:02 ` [LTP] [PATCH 4/4] syscalls/fanotify15: verify fid for dirent events Matthew Bobrowski
2019-04-16 14:29 ` Cyril Hrubis
2019-04-16 14:59 ` Amir Goldstein
2019-04-16 15:00 ` Cyril Hrubis
2019-04-18 18:36 ` Amir Goldstein
2019-04-18 18:58 ` Cyril Hrubis
2019-04-18 19:10 ` Amir Goldstein
2019-04-18 19:42 ` Cyril Hrubis
2019-04-19 7:18 ` Amir Goldstein
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=20190419083836.GB15974@lithium.mbobrowski.org \
--to=mbobrowski@mbobrowski.org \
--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