All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Lucas Bates <lucasb@mojatatu.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	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: [RFC net-next 1/1] tdc.py: Introduce required plugins
Date: Sat, 13 Apr 2019 01:37:18 +0200	[thread overview]
Message-ID: <15fd508c-0351-7332-805d-e536a7c77c17@6wind.com> (raw)
In-Reply-To: <CAMDBHYKEW0becbCxF4fSnpQLpbL-k7KiZqHnvaQxF=iYMEAWwg@mail.gmail.com>

Le 12/04/2019 à 18:07, Lucas Bates a écrit :
[snip]
> So something like this?  Note the usage of the keyword "requires",
> 
>     {
>         "id": "901f",
>         "name": "Add fw filter with prio at 32-bit maxixum",
>         "category": [
>             "filter",
>             "fw"
>         ],
>         "requires": ["nsPlugin"],
Yes.

>         "setup": [
>             "$TC qdisc add dev $DEV1 ingress"
>         ],
>         "cmdUnderTest": "$TC filter add dev $DEV1 parent ffff: handle
> 1 prio 65535 fw action ok",
>         "expExitCode": "0",
>         "verifyCmd": "$TC filter get dev $DEV1 parent ffff: handle 1
> prio 65535 protocol all fw",
>         "matchPattern": "pref 65535 fw.*handle 0x1.*gact action pass",
>         "matchCount": "1",
>         "teardown": [
>             "$TC qdisc del dev $DEV1 ingress"
>         ]
>     },


Regards,
Nicolas

  reply	other threads:[~2019-04-12 23:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 21:44 [RFC net-next 1/1] tdc.py: Introduce required plugins Lucas Bates
2019-04-10 14:33 ` Nicolas Dichtel
2019-04-11 20:54   ` Lucas Bates
2019-04-12  8:31     ` Nicolas Dichtel
2019-04-12 15:21       ` Lucas Bates
2019-04-12 15:42         ` Nicolas Dichtel
2019-04-12 16:07           ` Lucas Bates
2019-04-12 23:37             ` Nicolas Dichtel [this message]
2019-04-16 15:19               ` Lucas Bates

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=15fd508c-0351-7332-805d-e536a7c77c17@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=davem@davemloft.net \
    --cc=dcaratti@redhat.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=kernel@mojatatu.com \
    --cc=lucasb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.