From: Cong Wang <xiyou.wangcong@gmail.com>
To: "Yasuhara, Hiroyuki" <h.yasuhara@jp.fujitsu.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: netlink: question about netlink testsuite
Date: Tue, 18 Apr 2017 23:05:56 -0700 [thread overview]
Message-ID: <CAM_iQpVZ8f2Dc6xmLW3uzHe1AY+E3k-6cUXjnY678OCPmqAySg@mail.gmail.com> (raw)
In-Reply-To: <8B1169046A4CF54A85F712F74A617BA128039167@g01jpexmbkw01>
Hello,
On Tue, Apr 18, 2017 at 10:00 PM, Yasuhara, Hiroyuki
<h.yasuhara@jp.fujitsu.com> wrote:
> Hi,
>
> I'm looking for a testset about netlink function,
> for example, making a lot of netlink sockets and
> communicating with them in the testset.
>
> If anyone know such a testset, please give me the information.
>
libnl3 contains some test cases, which may be what you
are looking for:
https://github.com/thom311/libnl/tree/master/tests
next prev parent reply other threads:[~2017-04-19 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 5:00 netlink: question about netlink testsuite Yasuhara, Hiroyuki
2017-04-19 6:05 ` Cong Wang [this message]
2017-04-21 0:12 ` Yasuhara, Hiroyuki
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=CAM_iQpVZ8f2Dc6xmLW3uzHe1AY+E3k-6cUXjnY678OCPmqAySg@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=h.yasuhara@jp.fujitsu.com \
--cc=netdev@vger.kernel.org \
/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).