DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yang, GangX" <gangx.yang@intel.com>
To: "Jain, Deepak K" <deepak.k.jain@intel.com>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/openssl: add DES DOCSIS BPI support
Date: Fri, 3 Mar 2017 06:12:09 +0000	[thread overview]
Message-ID: <BD6A1439499EDC42898C5257367F506233D91927@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <A09C9DDE180C7E429EC68E2BFB95C903395444E3@IRSMSX107.ger.corp.intel.com>

Tested-by: Yang Gang < gangx.yang@intel.com >
- Check patch: success
- Apply patch: success
- compilation: success
      OS: fedora23
      GCC: gcc_x86-64, 5.3.1
      Commit: dpdk-next-crypto(081fefb01748e7063b1b9692af89d8115ec64632)
      x86_64-native-linuxapp-gcc: compile pass
- dts validation:
-- Test Commit: e5041333988936fdb09d578ec4fb7cb0ce796ecb
-- OS/Kernel: Fedora23/4.2.3-300.fc23.x86_64
-- GCC: gcc version 5.3.1
-- CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 1.80GHz
-- NIC: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ [8086:1572]
-- total 1,failed 0 (case1: contain cryptodev_openssl_autotest and all of others cryptodev cases on unit test . 
		   case 2: all of the related cases about openssl DES DOCSIS BPI cipher only on l2fwd-crypto test)

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jain, Deepak K
Sent: Tuesday, February 28, 2017 5:18 AM
To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Doherty, Declan <declan.doherty@intel.com>
Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/openssl: add DES DOCSIS BPI support


> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Thursday, February 23, 2017 3:22 PM
> To: Doherty, Declan <declan.doherty@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo 
> <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH v2] crypto/openssl: add DES DOCSIS BPI 
> support
> 
> Adds support in OpenSSL for algorithm following the DOCSIS 
> specification, which combines DES-CBC for full DES blocks (8 bytes) 
> and DES-CFB for last runt block (less than 8 bytes).
> 
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> This patch depends on patch http://dpdk.org/dev/patchwork/patch/20691/.
> 
> Changes in v2:
> - Added patch dependency note
> - Fixed the commit message
> --
> 2.7.4
Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>

  parent reply	other threads:[~2017-03-03  6:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 14:35 [dpdk-dev] [PATCH] " Pablo de Lara
2017-02-23 15:21 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2017-02-27 21:18   ` Jain, Deepak K
2017-03-01  9:01     ` Yang, GangX
2017-03-03  6:12     ` Yang, GangX [this message]
2017-03-30 16:53   ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2017-03-30 17:27     ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2017-03-30 18:37       ` De Lara Guarch, Pablo

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=BD6A1439499EDC42898C5257367F506233D91927@SHSMSX101.ccr.corp.intel.com \
    --to=gangx.yang@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=pablo.de.lara.guarch@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).