From: Petr Vorel <petr.vorel@gmail.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 0/3] fanotify musl fixes
Date: Wed, 13 Nov 2019 01:56:23 +0100 [thread overview]
Message-ID: <20191113005626.19585-1-petr.vorel@gmail.com> (raw)
Hi,
I generalized previous patch set a bit via autotools checks and also add
other cleanup (base decisions whether to define fallback definitions on
autotools checks).
BTW I tempted to use <linux/fanotify.h>, but not only we'd have to
define fanotify_mark(), but we'd also lost libc header testing.
https://travis-ci.org/pevik/ltp/builds/611138280
(openSUSE Tumbleweed failure is not related to this change)
Kind regards,
Petr
Petr Vorel (3):
fanotify: Move __kernel_fsid_t definition to correct place
fanotify: Rework checks for fallback definitions
fanotify: Detect val vs. __val fanotify_event_info_fid.fsid member
configure.ac | 1 +
m4/ltp-fanotify.m4 | 8 +++++
testcases/kernel/syscalls/fanotify/fanotify.h | 32 ++++++++++++-------
.../kernel/syscalls/fanotify/fanotify13.c | 8 ++---
.../kernel/syscalls/fanotify/fanotify15.c | 4 +--
5 files changed, 35 insertions(+), 18 deletions(-)
create mode 100644 m4/ltp-fanotify.m4
--
2.24.0
next reply other threads:[~2019-11-13 0:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 0:56 Petr Vorel [this message]
2019-11-13 0:56 ` [LTP] [PATCH v2 1/3] fanotify: Move __kernel_fsid_t definition to correct place Petr Vorel
2019-11-13 0:56 ` [LTP] [PATCH v2 2/3] fanotify: Rework checks for fallback definitions Petr Vorel
2019-11-13 0:56 ` [LTP] [PATCH v2 3/3] fanotify: Detect val vs. __val fanotify_event_info_fid.fsid member Petr Vorel
2019-11-13 5:58 ` [LTP] [PATCH v2 0/3] fanotify musl fixes Jan Stancek
2019-11-13 9:48 ` Cyril Hrubis
2019-11-14 18:17 ` Petr Vorel
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=20191113005626.19585-1-petr.vorel@gmail.com \
--to=petr.vorel@gmail.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