From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 2/4] Move fanotify fallback constants and structs to LAPI header
Date: Fri, 14 Oct 2022 00:08:00 +0200 [thread overview]
Message-ID: <Y0iMQEXsQbkNMwWf@pevik> (raw)
In-Reply-To: <20221013154935.20461-3-mdoucha@suse.cz>
Hi Martin,
although it will be used only by tests in testcases/kernel/syscalls/fanotify/,
it's cleaner to follow LTP approach.
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
...
> --- /dev/null
> +++ b/include/lapi/fanotify.h
> @@ -0,0 +1,210 @@
> +/* SPDX-License-Identifier: GPL-2.0-or-later */
> +/*
> + * Copyright (c) 2012-2020 Linux Test Project. All Rights Reserved.
FAN_FS_ERROR has been added in 3db153665 ("syscalls/fanotify22: Introduce FAN_FS_ERROR test")
which is 2022. Can be changed before merge.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-10-13 22:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:49 [LTP] [PATCH 0/4] Fix fanotify14 Martin Doucha
2022-10-13 15:49 ` [LTP] [PATCH 1/4] fanotify14: Print human-readable test case flags Martin Doucha
2022-10-13 21:36 ` Petr Vorel
2022-10-14 15:49 ` Martin Doucha
2022-10-14 16:17 ` Petr Vorel
2022-10-13 15:49 ` [LTP] [PATCH 2/4] Move fanotify fallback constants and structs to LAPI header Martin Doucha
2022-10-13 22:08 ` Petr Vorel [this message]
2022-10-14 15:56 ` Martin Doucha
2022-10-14 16:20 ` Petr Vorel
2022-10-13 15:49 ` [LTP] [PATCH 3/4] Add fanotify_get_supported_init_flags() helper function Martin Doucha
2022-10-14 6:15 ` Petr Vorel
2022-10-14 6:50 ` Amir Goldstein
2022-10-13 15:49 ` [LTP] [PATCH 4/4] fanotify14: Improve check for unsupported init flags Martin Doucha
2022-10-14 6:20 ` 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=Y0iMQEXsQbkNMwWf@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=mdoucha@suse.cz \
/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