From: David Miller <davem@davemloft.net>
To: xiyou.wangcong@gmail.com
Cc: lucasb@mojatatu.com, netdev@vger.kernel.org,
stephen@networkplumber.org, jiri@resnulli.us, mrv@mojatatu.com,
jhs@mojatatu.com
Subject: Re: [PATCH net-next 0/1] Introduction of the tc tests
Date: Tue, 20 Jun 2017 11:36:47 -0400 (EDT) [thread overview]
Message-ID: <20170620.113647.676648925381946650.davem@davemloft.net> (raw)
In-Reply-To: <CAM_iQpX-9No6RT1KEUJkd_smKjtxUJ1ZiYBwXOHJzR=1t_wBSA@mail.gmail.com>
From: Cong Wang <xiyou.wangcong@gmail.com>
Date: Mon, 19 Jun 2017 21:13:31 -0700
> I thought tools/testing/selftests/ is mainly for those tests close to
> kernel ABI and API. What is the criteria for these tests? If any test
> can fit in, we somehow would merge the whole LTP...
>
> I definitely don't object more tests, I am just wondering if we should
> put it to tools/testing/selftests/ or host it somewhere else.
I want it in the kernel so that it gets the level of exposure, care,
review, and use that the kernel does.
If you put it somewhere else it gets at least 10 times less of all
of those attributes.
next prev parent reply other threads:[~2017-06-20 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 21:22 [PATCH net-next 0/1] Introduction of the tc tests Lucas Bates
2017-06-16 21:22 ` [PATCH net-next 1/1] selftests: Introduce tc testsuite Lucas Bates
2017-06-19 23:37 ` [PATCH net-next 0/1] Introduction of the tc tests Cong Wang
2017-06-20 3:48 ` David Miller
2017-06-20 4:13 ` Cong Wang
2017-06-20 15:36 ` David Miller [this message]
2017-06-20 5:38 ` Stephen Hemminger
2017-06-20 5:40 ` Stephen Hemminger
2017-06-20 11:13 ` Jamal Hadi Salim
2017-06-20 17:16 ` David Miller
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=20170620.113647.676648925381946650.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=lucasb@mojatatu.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@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 NNTP newsgroup(s).