Linux Test Project
 help / color / mirror / Atom feed
From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/5] Convert CAN tests to new LTP API
Date: Mon, 18 Jan 2021 18:50:57 +0000	[thread overview]
Message-ID: <87h7neoz8u.fsf@suse.de> (raw)
In-Reply-To: <AM0PR05MB4642C547F8E6A3D5C230B87DECA40@AM0PR05MB4642.eurprd05.prod.outlook.com>

Hello Oliver,

Hartkopp, Oliver, Dr. (EESC/5) <oliver.hartkopp@volkswagen.de> writes:

> Dear Richard,
>
> either I'm not using my VW-Email for OSS/SocketCAN anymore and the
> socketcan-users@berlios is also not used anymore.

Thanks, I will send a V2 with these addresses removed from our docs.

>
> Please resend you patch set with these updated mail addresses:
>
> Oliver Hartkopp <socketcan@hartkopp.net>
> Linux-CAN ML <linux-can@vger.kernel.org>
>
> Many thanks,
> Oliver
>
> -----Urspr?ngliche Nachricht-----
> Von: Richard Palethorpe <rpalethorpe@suse.com> 
> Gesendet: Montag, 18. Januar 2021 16:56
> An: ltp@lists.linux.it
> Cc: socketcan-users@lists.berlios.de; Hartkopp, Oliver, Dr. (EESC/5) <oliver.hartkopp@volkswagen.de>; Richard Palethorpe <rpalethorpe@suse.com>
> Betreff: [PATCH 0/5] Convert CAN tests to new LTP API
>
> Hello,
>
> This is an attempt to convert the CAN tests to the (modern) LTP API and removes the wrapper script. 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.
>
> Richard Palethorpe (5):
>   API: Add FILE_SCANF to new lib
>   can: Add can_common.h for vcan device setup
>   can_filter: Convert to new library
>   can_recv_own_msgs: Convert to new library
>   can: Remove obsolete test wrapper script
>
>  include/tst_safe_file_ops.h                   |   3 +
>  testcases/network/can/Makefile                |   2 -
>  .../can/filter-tests/00_Descriptions.txt      |   1 +
>  testcases/network/can/filter-tests/INSTALL    |   3 +-
>  testcases/network/can/filter-tests/Makefile   |   2 -
>  .../network/can/filter-tests/can_common.h     |  70 ++++
>  .../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 ------
>  9 files changed, 288 insertions(+), 489 deletions(-)  create mode 100644 testcases/network/can/filter-tests/can_common.h
>  delete mode 100755 testcases/network/can/filter-tests/can_run_tests.sh


-- 
Thank you,
Richard.

      reply	other threads:[~2021-01-18 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-18 15:56 [LTP] [PATCH 0/5] Convert CAN tests to new LTP API Richard Palethorpe
2021-01-18 15:56 ` [LTP] [PATCH 1/5] API: Add FILE_SCANF to new lib Richard Palethorpe
2021-01-18 15:56 ` [LTP] [PATCH 2/5] can: Add can_common.h for vcan device setup Richard Palethorpe
2021-01-18 15:56 ` [LTP] [PATCH 3/5] can_filter: Convert to new library Richard Palethorpe
2021-01-18 15:56 ` [LTP] [PATCH 4/5] can_recv_own_msgs: " Richard Palethorpe
2021-01-18 15:56 ` [LTP] [PATCH 5/5] can: Remove obsolete test wrapper script Richard Palethorpe
2021-01-18 16:18 ` [LTP] [PATCH 0/5] Convert CAN tests to new LTP API Hartkopp, Oliver, Dr.
2021-01-18 18:50   ` Richard Palethorpe [this message]

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=87h7neoz8u.fsf@suse.de \
    --to=rpalethorpe@suse.de \
    --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