From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 5/5] doc/C-API: Update MNTPOINT related examples
Date: Wed, 31 Jan 2024 19:06:59 +0100 [thread overview]
Message-ID: <20240131180659.23587-6-pvorel@suse.cz> (raw)
In-Reply-To: <20240131180659.23587-1-pvorel@suse.cz>
MNTPOINT is defined in library header, no need to define it in the test.
Also actually use that definition instead of hardcoded value.
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
doc/C-Test-API.asciidoc | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/doc/C-Test-API.asciidoc b/doc/C-Test-API.asciidoc
index 5dc9516cf..321f9c534 100644
--- a/doc/C-Test-API.asciidoc
+++ b/doc/C-Test-API.asciidoc
@@ -165,9 +165,8 @@ libc and other low level libraries.
-------------------------------------------------------------------------------
static int fd0, fd1, mount_flag;
-#define MNTPOINT "mntpoint"
-#define FILE1 "mntpoint/file1"
-#define FILE2 "mntpoint/file2"
+#define FILE1 MNTPOINT"/file1"
+#define FILE2 MNTPOINT"/file2"
static void setup(void)
{
--
2.43.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-01-31 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 18:06 [LTP] [PATCH 0/5] MNTPOINT macro cleanup Petr Vorel
2024-01-31 18:06 ` [LTP] [PATCH 1/5] hugemmap: Move MNTPOINT definition to header Petr Vorel
2024-05-09 15:47 ` Cyril Hrubis
2024-05-10 12:59 ` Petr Vorel
2024-01-31 18:06 ` [LTP] [PATCH 2/5] tree: Define MNTPOINT in include/tst_fs.h Petr Vorel
2024-01-31 18:06 ` [LTP] [PATCH 3/5] tree: Reuse MNTPOINT definition Petr Vorel
2024-01-31 18:06 ` [LTP] [PATCH 4/5] tree: Use MNTPOINT macro instead of string Petr Vorel
2024-01-31 18:06 ` Petr Vorel [this message]
2024-05-09 16:18 ` [LTP] [PATCH 0/5] MNTPOINT macro cleanup Cyril Hrubis
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=20240131180659.23587-6-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).