From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kevin Laatz <kevin.laatz@intel.com>, dev@dpdk.org
Cc: bernard.iremonger@intel.com
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: add check for rx offload security flag
Date: Fri, 7 Sep 2018 12:13:43 +0100 [thread overview]
Message-ID: <95c40add-013f-e782-3e79-790cdcc50740@intel.com> (raw)
In-Reply-To: <20180904123256.61631-1-kevin.laatz@intel.com>
On 9/4/2018 1:32 PM, Kevin Laatz wrote:
> Add a check for the DEV_RX_OFFLOAD_SECURITY flag to the
> port_offload_cap_display().
>
> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2018-09-07 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 12:32 Kevin Laatz
2018-09-07 11:13 ` Ferruh Yigit [this message]
2018-09-10 16:16 ` Iremonger, Bernard
2018-09-10 16:28 ` [dpdk-dev] [PATCH v2] app/testpmd: add check for Rx " Kevin Laatz
2018-09-10 16:55 ` Iremonger, Bernard
2018-09-21 0:51 ` Ferruh Yigit
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=95c40add-013f-e782-3e79-790cdcc50740@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@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 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).