From: Petr Vorel <pvorel@suse.cz>
To: automated-testing@lists.yoctoproject.org
Cc: ltp@lists.linux.it, linux-sctp@vger.kernel.org,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>,
Xin Long <lucien.xin@gmail.com>,
Anders Roxell <anders.roxell@linaro.org>,
Philip Li <philip.li@intel.com>, Tim Bird <tim.bird@sony.com>,
Cyril Hrubis <chrubis@suse.cz>, Li Wang <liwang@redhat.com>,
Jan Stancek <jstancek@redhat.com>,
Baruch Siach <baruch@tkos.co.il>,
Erico Nunes <nunes.erico@gmail.com>,
Kory Maincent <kory.maincent@bootlin.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Veronika Kabatova <vkabatov@redhat.com>,
Joerg Vehlow <joerg.vehlow@aox-tech.de>
Subject: SCTP testing
Date: Thu, 3 Feb 2022 18:48:35 +0100 [thread overview]
Message-ID: <YfwVcwpZU/lusVlC@pevik> (raw)
Hi all,
we've been just discussing, which repository should be hosting SCTP tests [1].
Do you use these SCTP tests? If yes, do you use it from LTP [2] or the official
SCTP kernel developers repository [3] ? If you use integrated to some testing
framework, would it be a problem if repository changes?
Also, do you use LTP network tests at all?
Kind regards,
Petr
[1] https://lore.kernel.org/linux-sctp/YfpnVfrto4Elshy5@pevik/
[2] https://github.com/linux-test-project/ltp/tree/master/utils/sctp
[3] https://github.com/sctp/lksctp-tools
next reply other threads:[~2022-02-03 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 17:48 Petr Vorel [this message]
2022-02-04 13:29 ` [Automated-testing] SCTP testing Veronika Kabatova
2022-02-08 18:50 ` Petr Vorel
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=YfwVcwpZU/lusVlC@pevik \
--to=pvorel@suse.cz \
--cc=anders.roxell@linaro.org \
--cc=automated-testing@lists.yoctoproject.org \
--cc=baruch@tkos.co.il \
--cc=chrubis@suse.cz \
--cc=joerg.vehlow@aox-tech.de \
--cc=jstancek@redhat.com \
--cc=kory.maincent@bootlin.com \
--cc=linux-sctp@vger.kernel.org \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=nhorman@tuxdriver.com \
--cc=nunes.erico@gmail.com \
--cc=philip.li@intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tim.bird@sony.com \
--cc=vkabatov@redhat.com \
--cc=vyasevich@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).