netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Bates <lucasb@mojatatu.com>
To: Alexander Aring <aring@mojatatu.com>
Cc: David Miller <davem@davemloft.net>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Marcelo Ricardo Leitner <mleitner@redhat.com>,
	Vlad Buslov <vladbu@mellanox.com>,
	Davide Caratti <dcaratti@redhat.com>,
	kernel@mojatatu.com
Subject: Re: [PATCH v2 net-next 1/3] tc-testing: Add JSON verification to tdc
Date: Mon, 8 Jul 2019 21:17:48 -0400	[thread overview]
Message-ID: <CAMDBHYKyV2CH=1yV16hj0xaBkAp2nRjc1PoXRj6OE=0ykOp9VA@mail.gmail.com> (raw)
In-Reply-To: <20190708172458.syopc3bvvkjb3sxv@x220t>

On Mon, Jul 8, 2019 at 1:25 PM Alexander Aring <aring@mojatatu.com> wrote:
> > Unless I'm off-base here?
>
> yes you need to know some python, complex code can be hidden by some
> helper functionality I guess.
>
> I have no problem to let this patch in, it will not harm anything...
I think I'm going to pull it for the moment - I started thinking about
the patch today and I think it needs more testing against larger
amounts of data.

> Maybe I work on a matchEval and show some examples... in a human
> readable way you can even concatenate bool expressions in combinations
> with helpers.
>
> I just was curious, so I might add the matchEval or something to show
> this approach.

Go for it, I think you have a much better grasp on the use of eval
than I do - and it could be very useful for test cases.

  reply	other threads:[~2019-07-09  1:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04  0:44 [PATCH v2 net-next 0/3] tc-testing: Add JSON verification and simple traffic generation Lucas Bates
2019-07-04  0:45 ` [PATCH v2 net-next 1/3] tc-testing: Add JSON verification to tdc Lucas Bates
2019-07-04 20:21   ` Alexander Aring
2019-07-08 16:48     ` Lucas Bates
2019-07-08 17:24       ` Alexander Aring
2019-07-09  1:17         ` Lucas Bates [this message]
2019-07-04  0:45 ` [PATCH v2 net-next 2/3] tc-testing: Allow tdc plugins to see test case data Lucas Bates
2019-07-04  0:45 ` [PATCH v2 net-next 3/3] tc-testing: introduce scapyPlugin for basic traffic Lucas Bates
2019-07-04 20:29   ` Alexander Aring
2019-07-09  1:28     ` Lucas Bates
2019-07-09 15:10       ` Alexander Aring
2019-07-08  1:57 ` [PATCH v2 net-next 0/3] tc-testing: Add JSON verification and simple traffic generation 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='CAMDBHYKyV2CH=1yV16hj0xaBkAp2nRjc1PoXRj6OE=0ykOp9VA@mail.gmail.com' \
    --to=lucasb@mojatatu.com \
    --cc=aring@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel@mojatatu.com \
    --cc=mleitner@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@mellanox.com \
    --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).