DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] null_crypto_pmd: PMD to support null crypto operations
Date: Fri, 11 Mar 2016 01:05:37 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8C86A0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <6924173.bP3VpQxJv8@xps13>



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, March 11, 2016 12:56 AM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4] null_crypto_pmd: PMD to support null
> crypto operations
> 
> Sorry, we need a v5
> 
> 2016-03-11 00:50, Pablo de Lara:
> > +Null Crypto PMD
> > +M: Declan Doherty <declan.doherty@intel.com>
> > +F: drivers/crypto/null/
> > +F: doc/guides/cryptodevs/snow3g.rst
> 
> Not the right doc.
> The null doc is not in this patch BTW.
> 
> Missing blank line (2 before next section).
> >
> >  Packet processing
> >  -----------------
> 

Done. Sorry for the extra versions.

  reply	other threads:[~2016-03-11  1:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-31 20:48 [dpdk-dev] [PATCH] " Declan Doherty
2016-03-10 16:46 ` [dpdk-dev] [PATCH v2] " Pablo de Lara
2016-03-10 16:49   ` Jain, Deepak K
2016-03-11  0:39   ` De Lara Guarch, Pablo
2016-03-11  0:43   ` [dpdk-dev] [PATCH v3] " Pablo de Lara
2016-03-11  0:45     ` De Lara Guarch, Pablo
2016-03-11  0:50     ` [dpdk-dev] [PATCH v4] " Pablo de Lara
2016-03-11  0:56       ` Thomas Monjalon
2016-03-11  1:05         ` De Lara Guarch, Pablo [this message]
2016-03-11  1:04       ` [dpdk-dev] [PATCH v5] " Pablo de Lara
2016-03-11  1:15         ` Thomas Monjalon

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=E115CCD9D858EF4F90C690B0DCB4D8973C8C86A0@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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).