From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Cc: linux-can@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>,
Richard Palethorpe <rpalethorpe@suse.com>,
Cyril Hrubis <chrubis@suse.cz>, Petr Vorel <pvorel@suse.cz>
Subject: [PATCH v4 1/7] API: Add FILE_SCANF to new lib
Date: Fri, 29 Jan 2021 17:02:59 +0000 [thread overview]
Message-ID: <20210129170305.27383-2-rpalethorpe@suse.com> (raw)
In-Reply-To: <20210129170305.27383-1-rpalethorpe@suse.com>
Signed-off-by: Richard Palethorpe <rpalethorpe@suse.com>
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
Reviewed-by: Petr Vorel <pvorel@suse.cz>
---
include/tst_safe_file_ops.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/tst_safe_file_ops.h b/include/tst_safe_file_ops.h
index 894c16123..ea8f89263 100644
--- a/include/tst_safe_file_ops.h
+++ b/include/tst_safe_file_ops.h
@@ -7,6 +7,9 @@
#include "safe_file_ops_fn.h"
+#define FILE_SCANF(path, fmt, ...) \
+ file_scanf(__FILE__, __LINE__, (path), (fmt), ## __VA_ARGS__)
+
#define SAFE_FILE_SCANF(path, fmt, ...) \
safe_file_scanf(__FILE__, __LINE__, NULL, \
(path), (fmt), ## __VA_ARGS__)
--
2.30.0
next prev parent reply other threads:[~2021-01-29 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 17:02 [PATCH v4 0/7] Convert CAN tests to new LTP API Richard Palethorpe
2021-01-29 17:02 ` Richard Palethorpe [this message]
2021-01-29 17:03 ` [PATCH v4 2/7] can: Add can_common.h for vcan device setup Richard Palethorpe
2021-01-29 17:03 ` [PATCH v4 3/7] can: Add COPYING with dual license text Richard Palethorpe
2021-01-29 17:03 ` [PATCH v4 4/7] can_filter: Convert to new library Richard Palethorpe
2021-01-29 17:03 ` [PATCH v4 5/7] can_recv_own_msgs: " Richard Palethorpe
2021-01-29 17:03 ` [PATCH v4 6/7] can: Remove obsolete test wrapper script Richard Palethorpe
2021-01-29 17:03 ` [PATCH v4 7/7] can: Update contact details Richard Palethorpe
2021-02-01 15:21 ` [LTP] [PATCH v4 0/7] Convert CAN tests to new LTP API 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=20210129170305.27383-2-rpalethorpe@suse.com \
--to=rpalethorpe@suse.com \
--cc=chrubis@suse.cz \
--cc=linux-can@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
--cc=socketcan@hartkopp.net \
/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 NNTP newsgroup(s).