From: Petr Vorel <pvorel@suse.cz>
To: linux-sctp@vger.kernel.org, ltp@lists.linux.it,
Cyril Hrubis <chrubis@suse.cz>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Xin Long <lucien.xin@gmail.com>,
Vlad Yasevich <vyasevich@gmail.com>,
Neil Horman <nhorman@tuxdriver.com>,
Martin Doucha <martin.doucha@suse.com>
Subject: Re: [LTP] [RFC] SCTP tests in LTP vs. on github.com/sctp
Date: Wed, 2 Feb 2022 12:29:33 +0100 [thread overview]
Message-ID: <YfprHQcxAnsb1RI/@pevik> (raw)
In-Reply-To: <YfpnVfrto4Elshy5@pevik>
FYI we've been thinking about back in 2013.
https://lore.kernel.org/ltp/20130805121135.GB8739@rei/
I'd personally prefer sctp folks maintain them and we removed them from LTP.
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-02-02 11:30 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 [this message]
2022-02-02 12:28 ` Marcelo Ricardo Leitner
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=YfprHQcxAnsb1RI/@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=linux-sctp@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=martin.doucha@suse.com \
--cc=nhorman@tuxdriver.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