From: Felix Maurer <fmaurer@redhat.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
linux-can@vger.kernel.org
Cc: Davide Caratti <dcaratti@redhat.com>,
Filippo Storniolo <fstornio@redhat.com>
Subject: Advancing the testing for the CAN subsystem
Date: Thu, 20 Feb 2025 14:03:57 +0100 [thread overview]
Message-ID: <0feda774-853b-42c3-8bae-5d84f7881171@redhat.com> (raw)
Hi Marc, Oliver, and linux-can community,
we are reaching out to you because we would like to advance the testing
of the kernel CAN subsystem. We, that's Davide, Filippo and I, are
volunteering to provide the patches for this, but would like to get your
feedback and opinions first.
We know about the can-tests repository[1] and think this is a good
starting point for our efforts. Currently, there are two main activities
we'd like to do:
- Promote the test cases in can-tests to become part of the kernel
selftests: This would mainly get the tests closer to the upstream kernel
development, both in terms of maintenance and actually running them. CI
systems like LKFT and CKI could easily be continuously running the
tests. The downside is that existing automation depending on can-tests
(which we don't know about) would need to be modified.
- Extend the coverage of the tests: This could include testing for,
e.g., vcan, vxcan, and the cangw netlink interface. But we're open to
feedback here if you see any pressing areas.
Like I stated in the beginning, this message should get the discussion
started and we are looking forward to your feedback or concerns on these
ideas.
Thanks,
Felix
[1]: https://github.com/linux-can/can-tests
next reply other threads:[~2025-02-20 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:03 Felix Maurer [this message]
2025-02-21 8:04 ` Advancing the testing for the CAN subsystem Oliver Hartkopp
2025-02-24 14:17 ` Felix Maurer
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=0feda774-853b-42c3-8bae-5d84f7881171@redhat.com \
--to=fmaurer@redhat.com \
--cc=dcaratti@redhat.com \
--cc=fstornio@redhat.com \
--cc=linux-can@vger.kernel.org \
--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