From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Declan Doherty <declan.doherty@intel.com>
Subject: Re: [PATCH v7 2/4] ethdev: Add group JUMP action
Date: Thu, 26 Apr 2018 20:54:03 +0200 [thread overview]
Message-ID: <7612186.gDT3Kgd9DL@xps> (raw)
In-Reply-To: <20180426172919.8450-3-declan.doherty@intel.com>
About title, we use uppercase only for acronyms.
So it should be:
ethdev: add group jump action
next prev parent reply other threads:[~2018-04-26 18:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 12:08 [PATCH v6 0/4] additions to support tunnel encap/decap Declan Doherty
2018-04-26 12:08 ` [PATCH v6 1/4] ethdev: Add tunnel encap/decap actions Declan Doherty
2018-04-26 12:08 ` [PATCH v6 2/4] ethdev: Add group JUMP action Declan Doherty
2018-04-26 12:08 ` [PATCH v6 3/4] ethdev: add mark flow item to rte_flow_item_types Declan Doherty
2018-04-26 12:08 ` [PATCH v6 4/4] ethdev: add shared counter support to rte_flow Declan Doherty
2018-04-26 14:06 ` Ori Kam
2018-04-26 14:27 ` Ferruh Yigit
2018-04-26 14:43 ` Ori Kam
2018-04-26 14:48 ` Doherty, Declan
2018-04-26 17:29 ` [PATCH v7 0/4] " Declan Doherty
2018-04-26 17:29 ` [PATCH v7 1/4] ethdev: Add tunnel encap/decap actions Declan Doherty
2018-04-26 17:29 ` [PATCH v7 2/4] ethdev: Add group JUMP action Declan Doherty
2018-04-26 18:54 ` Thomas Monjalon [this message]
2018-04-27 12:24 ` Ferruh Yigit
2018-04-26 17:29 ` [PATCH v7 3/4] ethdev: add mark flow item to rte_flow_item_types Declan Doherty
2018-04-26 18:52 ` Thomas Monjalon
2018-04-27 12:24 ` Ferruh Yigit
2018-04-26 17:29 ` [PATCH v7 4/4] ethdev: add shared counter support to rte_flow Declan Doherty
2018-04-26 18:55 ` Thomas Monjalon
2018-04-27 12:25 ` Ferruh Yigit
2018-04-27 14:52 ` Ferruh Yigit
2018-04-26 20:58 ` [PATCH v7 0/4] " Ferruh Yigit
2018-04-27 20:18 ` [PATCH v6 0/4] additions to support tunnel encap/decap Michael Wildt
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=7612186.gDT3Kgd9DL@xps \
--to=thomas@monjalon.net \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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.