From: David Miller <davem@davemloft.net>
To: bjb@mojatatu.com
Cc: kernel@mojatatu.com, xiyou.wangcong@gmail.com, jiri@resnulli.us,
chrism@mellanox.com, lucasb@mojatatu.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/7] tools: tc-testing: Plugin Architecture
Date: Thu, 15 Feb 2018 15:38:57 -0500 (EST) [thread overview]
Message-ID: <20180215.153857.49672271575245351.davem@davemloft.net> (raw)
In-Reply-To: <20180214190925.20195-1-bjb@mojatatu.com>
From: "Brenda J. Butler" <bjb@mojatatu.com>
Date: Wed, 14 Feb 2018 14:09:18 -0500
> To make tdc.py more general, we are introducing a plugin architecture.
>
> This patch set first organizes the command line parameters, then
> introduces the plugin architecture and some example plugins.
Series applied, thanks Brenda.
prev parent reply other threads:[~2018-02-15 20:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 19:09 [PATCH net-next 0/7] tools: tc-testing: Plugin Architecture Brenda J. Butler
2018-02-14 19:09 ` [PATCH net-next 1/7] tools: tc-testing: Command line parms Brenda J. Butler
2018-02-14 22:43 ` Lucas Bates
2018-02-14 19:09 ` [PATCH net-next 2/7] tools: tc-testing: Refactor test-runner Brenda J. Butler
2018-02-14 22:44 ` Lucas Bates
2018-02-14 19:09 ` [PATCH net-next 3/7] tools: tc-testing: Introduce plugin architecture Brenda J. Butler
2018-02-14 22:44 ` Lucas Bates
2018-02-14 19:09 ` [PATCH net-next 4/7] tools: tc-testing: rootPlugin Brenda J. Butler
2018-02-14 22:44 ` Lucas Bates
2018-02-14 19:09 ` [PATCH net-next 5/7] tools: tc-testing: nsPlugin Brenda J. Butler
2018-02-14 22:45 ` Lucas Bates
2018-02-14 19:09 ` [PATCH net-next 6/7] tools: tc-testing: valgrindPlugin Brenda J. Butler
2018-02-14 22:45 ` Lucas Bates
2018-02-14 19:09 ` [PATCH net-next 7/7] tools: tc-testing: Update README and TODO Brenda J. Butler
2018-02-14 22:46 ` Lucas Bates
2018-02-15 20:38 ` David Miller [this message]
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=20180215.153857.49672271575245351.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bjb@mojatatu.com \
--cc=chrism@mellanox.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=lucasb@mojatatu.com \
--cc=netdev@vger.kernel.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).