From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Petr Vorel <pvorel@suse.cz>
Cc: Xin Long <lucien.xin@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Vlad Yasevich <vyasevich@gmail.com>,
linux-sctp@vger.kernel.org,
Martin Doucha <martin.doucha@suse.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [RFC] SCTP tests in LTP vs. on github.com/sctp
Date: Wed, 2 Feb 2022 09:28:36 -0300 [thread overview]
Message-ID: <Yfp49PCW9Res5gXG@t14s.localdomain> (raw)
In-Reply-To: <YfpnVfrto4Elshy5@pevik>
Hi Petr,
On Wed, Feb 02, 2022 at 12:13:25PM +0100, Petr Vorel wrote:
> Hi all,
>
> SCTP tests lksctp-tools [1] are also in LTP [2].
> IMHO it's not worth to have it on both places.
Agree. I wasn't aware of the copy in LTP, btw.
A question I have now is, is getting more exposure because it is in
LTP? As in, does it get executed periodically by bots somewhere?
>
> lksctp-tools looks like to be the official ones [3] so maybe drop it from LTP?
>
> Version in LTP was updated to 1.0.15 some time ago (upstream has 1.0.19, containing various fixes [4],
> maybe worth to be backported to lksctp-tools? Frankly speaking even being older
> version the LTP code looks to me better. One test was even rewritten to LTP new
> C API [5] in order to apply more improvements [6].
>
> BTW I'd really recommend lksctp-tools project to take new LTP C API [7] and
> rewrite tests into it. But are these tests still relevant? (is it worth of
> work?)
These are nice tips, thanks. We certainly can have a take on them.
Best regards,
Marcelo
>
> Kind regards,
> Petr
>
> [1] https://github.com/sctp/lksctp-tools
> [2] https://github.com/linux-test-project/ltp/tree/master/utils/sctp
> [3] https://github.com/sctp
> [4] https://github.com/linux-test-project/ltp/commits/master/utils/sctp
> [5] https://github.com/linux-test-project/ltp/commit/fcd43b3dd7a8e8fab2b03ec9fa659f21ff5cecb2
> [6] https://github.com/linux-test-project/ltp/commit/fcd43b3dd7a8e8fab2b03ec9fa659f21ff5cecb2
> [7] https://github.com/linux-test-project/ltp/wiki/C-Test-API
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-02-02 12:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 11:13 [LTP] [RFC] SCTP tests in LTP vs. on github.com/sctp Petr Vorel
2022-02-02 11:29 ` Petr Vorel
2022-02-02 12:28 ` Marcelo Ricardo Leitner [this message]
2022-02-02 13:32 ` Petr Vorel
2022-02-03 11:12 ` 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=Yfp49PCW9Res5gXG@t14s.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=lucien.xin@gmail.com \
--cc=martin.doucha@suse.com \
--cc=nhorman@tuxdriver.com \
--cc=pvorel@suse.cz \
--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