DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"Nicolau, Radu" <radu.nicolau@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Zhao, XinfengX" <xinfengx.zhao@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: check if security capabilities are enabled by HW
Date: Sat, 20 Jan 2018 09:45:22 +0000	[thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71AD14708@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772588627F305@irsmsx105.ger.corp.intel.com>



> -----Original Message-----
> From: Zhang, Helin
> Sent: Thursday, January 18, 2018 8:43 AM
> To: Ananyev, Konstantin; Nicolau, Radu; dev@dpdk.org
> Cc: Yigit, Ferruh; Lu, Wenzhuo; Zhao, XinfengX; De Lara Guarch, Pablo
> Subject: RE: [PATCH v2] net/ixgbe: check if security capabilities are enabled by
> HW
> 
> 
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ananyev,
> > Konstantin
> > Sent: Thursday, January 18, 2018 6:48 AM
> > To: Nicolau, Radu; dev@dpdk.org
> > Cc: Yigit, Ferruh; Lu, Wenzhuo; Zhao, XinfengX; De Lara Guarch, Pablo
> > Subject: Re: [dpdk-dev] [PATCH v2] net/ixgbe: check if security
> > capabilities are enabled by HW
> >
> >
> >
> > > -----Original Message-----
> > > From: Nicolau, Radu
> > > Sent: Wednesday, January 17, 2018 11:55 AM
> > > To: dev@dpdk.org
> > > Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Lu, Wenzhuo
> > > <wenzhuo.lu@intel.com>; Ananyev, Konstantin
> > > <konstantin.ananyev@intel.com>; Zhao, XinfengX
> > > <xinfengx.zhao@intel.com>; De Lara Guarch, Pablo
> > > <pablo.de.lara.guarch@intel.com>; Nicolau, Radu
> > > <radu.nicolau@intel.com>
> > > Subject: [PATCH v2] net/ixgbe: check if security capabilities are
> > > enabled by HW
> > >
> > > Check if the security enable bits are not fused before setting
> > > offload capabilities for security
> > >
> > > Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
> > > ---
> >
> > Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Applied to dpdk-next-net-intel, with minor commit title changes. Thanks!
Removed from dpdk-next-net-intel, as new version was sent out. Thanks!

/Helin
> 
> /Helin

  parent reply	other threads:[~2018-01-20  9:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 11:19 [dpdk-dev] [PATCH] " Radu Nicolau
2018-01-17 11:34 ` Ananyev, Konstantin
2018-01-17 11:40   ` Nicolau, Radu
2018-01-17 11:54 ` [dpdk-dev] [PATCH v2] " Radu Nicolau
2018-01-17 22:47   ` Ananyev, Konstantin
2018-01-18  0:43     ` Zhang, Helin
2018-01-18 14:58       ` Ferruh Yigit
2018-01-20  9:45     ` Zhang, Helin [this message]
2018-01-18 12:46   ` [dpdk-dev] [PATCH v3] net/ixgbe: check security enable bits Radu Nicolau
2018-01-22 10:23     ` Ananyev, Konstantin
2018-01-23  2:06       ` Zhang, Helin

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=F35DEAC7BCE34641BA9FAC6BCA4A12E71AD14708@SHSMSX103.ccr.corp.intel.com \
    --to=helin.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=radu.nicolau@intel.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=xinfengx.zhao@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).