From: Thomas Monjalon <thomas@monjalon.net>
To: Alexander Kozyrev <akozyrev@nvidia.com>
Cc: dev@dpdk.org, viacheslavo@nvidia.com, orika@nvidia.com,
ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru,
jerinjacobk@gmail.com, ajit.khaparde@broadcom.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add IPv6 DSCP option for modify_field action
Date: Tue, 26 Jan 2021 09:27:13 +0100 [thread overview]
Message-ID: <2737358.nkdc06BFcE@thomas> (raw)
In-Reply-To: <20210126044034.15301-1-akozyrev@nvidia.com>
26/01/2021 05:40, Alexander Kozyrev:
> Support IPv6 DSCP modification via the modify_field action.
> Add the ipv6_dscp option for the corresponding header field.
>
> Fixes: 24e1a5e39df ("app/testpmd: support modify field flow action")
>
> Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
> ---
> app/test-pmd/cmdline_flow.c | 2 +-
It should be squashed with the patch adding the field in ethdev.
prev parent reply other threads:[~2021-01-26 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 4:40 Alexander Kozyrev
2021-01-26 8:27 ` Thomas Monjalon [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=2737358.nkdc06BFcE@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=akozyrev@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=orika@nvidia.com \
--cc=viacheslavo@nvidia.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).