From: Richard Palethorpe <rpalethorpe@suse.com>
To: ltp@lists.linux.it
Cc: linux-can@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Richard Palethorpe <rpalethorpe@suse.com>
Subject: [PATCH v3 0/7] Convert CAN tests to new LTP API
Date: Wed, 20 Jan 2021 14:37:16 +0000 [thread overview]
Message-ID: <20210120143723.26483-1-rpalethorpe@suse.com> (raw)
Hello,
This is an attempt to convert the CAN tests to the (modern) Linux Test
Project API and removes the wrapper script. To be clear, this is a
patch-set for the LTP *not* the kernel tree or can-utils.
I have tried to keep the core test behaviour the same, but (for
example) moving to the SAFE_ functions will naturally introduce some
changes in error checking. Deliberate behavioral changes have been
noted in the commit messages.
FYI, we appear to have 4 CAN tests in LTP including two tests for
SLCAN (pty03, pty04).
V2: Update e-mail addresses and resend
V3:
* Add COPYING and use dual license SPDX identifier
* Fix compilation issues with can_common.h
Richard Palethorpe (7):
API: Add FILE_SCANF to new lib
can: Add can_common.h for vcan device setup
can: Add COPYING with dual license text
can_filter: Convert to new library
can_recv_own_msgs: Convert to new library
can: Remove obsolete test wrapper script
can: Update contact details
include/tst_safe_file_ops.h | 3 +
testcases/network/can/Makefile | 2 -
.../can/filter-tests/00_Descriptions.txt | 6 +-
testcases/network/can/filter-tests/COPYING | 35 ++
testcases/network/can/filter-tests/INSTALL | 3 +-
testcases/network/can/filter-tests/Makefile | 4 -
.../network/can/filter-tests/can_common.h | 75 +++++
.../network/can/filter-tests/can_filter.c | 317 +++++++-----------
.../can/filter-tests/can_rcv_own_msgs.c | 273 +++++----------
.../network/can/filter-tests/can_run_tests.sh | 106 ------
10 files changed, 331 insertions(+), 493 deletions(-)
create mode 100644 testcases/network/can/filter-tests/COPYING
create mode 100644 testcases/network/can/filter-tests/can_common.h
delete mode 100755 testcases/network/can/filter-tests/can_run_tests.sh
--
2.30.0
next reply other threads:[~2021-01-20 14:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 14:37 Richard Palethorpe [this message]
2021-01-20 14:37 ` [PATCH v3 1/7] API: Add FILE_SCANF to new lib Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 2/7] can: Add can_common.h for vcan device setup Richard Palethorpe
2021-01-25 10:20 ` Oliver Hartkopp
2021-01-25 10:59 ` Richard Palethorpe
2021-01-26 21:28 ` Petr Vorel
2021-01-27 7:52 ` Oliver Hartkopp
2021-01-27 8:18 ` Richard Palethorpe
2021-01-27 12:13 ` Petr Vorel
2021-01-27 15:07 ` [LTP] " Petr Vorel
2021-01-20 14:37 ` [PATCH v3 3/7] can: Add COPYING with dual license text Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 4/7] can_filter: Convert to new library Richard Palethorpe
2021-01-20 14:37 ` [PATCH v3 5/7] can_recv_own_msgs: " Richard Palethorpe
2021-01-25 14:29 ` [LTP] " Cyril Hrubis
2021-01-20 14:37 ` [PATCH v3 6/7] can: Remove obsolete test wrapper script Richard Palethorpe
2021-01-25 9:10 ` [LTP] " Petr Vorel
2021-01-20 14:37 ` [PATCH v3 7/7] can: Update contact details Richard Palethorpe
2021-01-25 10:25 ` Oliver Hartkopp
2021-01-25 14:30 ` [LTP] " 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=20210120143723.26483-1-rpalethorpe@suse.com \
--to=rpalethorpe@suse.com \
--cc=linux-can@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=mkl@pengutronix.de \
--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