From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] include: Move new API only functions to new API header
Date: Tue, 2 Jan 2024 23:39:34 +0100 [thread overview]
Message-ID: <20240102223935.1012840-1-pvorel@suse.cz> (raw)
create_overlay_dirs() and mount_overlay() were implemented only in new
API (and we are not planning to use them in legacy API), thus remove
them from legacy API header.
Fixes: a88bbb43d ("lib: add helpers to setup overlayfs mountpoint")
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
include/safe_file_ops_fn.h | 4 ----
include/tst_safe_file_ops.h | 6 ++++++
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/include/safe_file_ops_fn.h b/include/safe_file_ops_fn.h
index aa6420d90..223fb0d68 100644
--- a/include/safe_file_ops_fn.h
+++ b/include/safe_file_ops_fn.h
@@ -90,8 +90,4 @@ int safe_touch(const char *file, const int lineno,
const char *pathname,
mode_t mode, const struct timespec times[2]);
-/* helper functions to setup overlayfs mountpoint */
-void create_overlay_dirs(void);
-int mount_overlay(const char *file, const int lineno, int strict);
-
#endif /* SAFE_FILE_OPS_FN */
diff --git a/include/tst_safe_file_ops.h b/include/tst_safe_file_ops.h
index 62f6600ec..401f6ee25 100644
--- a/include/tst_safe_file_ops.h
+++ b/include/tst_safe_file_ops.h
@@ -56,6 +56,12 @@
safe_touch(__FILE__, __LINE__, NULL, \
(pathname), (mode), (times))
+/* New API only functions */
+
+/* helper functions to setup overlayfs mountpoint */
+void create_overlay_dirs(void);
+int mount_overlay(const char *file, const int lineno, int strict);
+
#define SAFE_MOUNT_OVERLAY() \
((void) mount_overlay(__FILE__, __LINE__, 1))
--
2.43.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2024-01-02 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 22:39 Petr Vorel [this message]
2024-01-02 22:39 ` [LTP] [PATCH 2/2] tst_fs_setup.c: Add tst_ prefix to new API functions Petr Vorel
2024-02-26 14:20 ` Cyril Hrubis
2024-03-13 14:12 ` Martin Doucha
2024-03-13 21:15 ` 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=20240102223935.1012840-1-pvorel@suse.cz \
--to=pvorel@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).