From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/3] expand txtimestamp selftest
Date: Thu, 20 Dec 2018 16:22:51 -0500 [thread overview]
Message-ID: <20181220212254.125681-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Convert the existing txtimestamp test to run as part of kselftest
and return a pass/fail.
Also expand the variations of timestamping tested, including packet
sockets, ipv6 raw and dgram and passing options using cmsg.
These are enough changes to split across a few patches, even if all
changes are only this one test.
Willem de Bruijn (3):
selftests: expand txtimestamp with cmsg support
selftests: expand txtimestamp with ipv6 dgram + raw and pf_packet
selftests: add txtimestamp kselftest
tools/testing/selftests/Makefile | 1 +
.../networking/timestamping/Makefile | 5 +-
.../selftests/networking/timestamping/config | 2 +
.../networking/timestamping/txtimestamp.c | 382 ++++++++++++++----
.../networking/timestamping/txtimestamp.sh | 58 +++
5 files changed, 368 insertions(+), 80 deletions(-)
create mode 100644 tools/testing/selftests/networking/timestamping/config
create mode 100755 tools/testing/selftests/networking/timestamping/txtimestamp.sh
--
2.20.1.415.g653613c723-goog
next reply other threads:[~2018-12-20 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 21:22 Willem de Bruijn [this message]
2018-12-20 21:22 ` [PATCH net-next 1/3] selftests: expand txtimestamp with cmsg support Willem de Bruijn
2018-12-20 21:22 ` [PATCH net-next 2/3] selftests: expand txtimestamp with ipv6 dgram + raw and pf_packet Willem de Bruijn
2018-12-20 21:22 ` [PATCH net-next 3/3] selftests: add txtimestamp kselftest Willem de Bruijn
2018-12-21 1:27 ` [PATCH net-next 0/3] expand txtimestamp selftest David Miller
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=20181220212254.125681-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
/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).