DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>,
	"Griffin, John" <john.griffin@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/qat: add Intel(R) QuickAssist C3xxx device
Date: Wed, 7 Sep 2016 19:34:52 +0000	[thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C9033942A08D@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8973C9D5D94@IRSMSX108.ger.corp.intel.com>

HI Pablo,

> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Wednesday, September 7, 2016 7:08 PM
> To: Jain, Deepak K <deepak.k.jain@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; Griffin, John <john.griffin@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] crypto/qat: add Intel(R) QuickAssist C3xxx device
> 
> Hi Deepak,
> 
> > -----Original Message-----
> > From: Jain, Deepak K
> > Sent: Friday, August 26, 2016 5:28 AM
> > To: Trahe, Fiona; Griffin, John; De Lara Guarch, Pablo
> > Cc: dev@dpdk.org; Jain, Deepak K
> > Subject: [PATCH] crypto/qat: add Intel(R) QuickAssist C3xxx device
> >
> > Signed-off-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
> 
> Could you send a v2 with a release notes update?
> 
Agreed. I will send v2 with release notes.

> Thanks,
> Pablo

  reply	other threads:[~2016-09-07 19:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 12:27 Deepak Kumar Jain
2016-08-26 13:06 ` Trahe, Fiona
2016-09-07 18:07 ` De Lara Guarch, Pablo
2016-09-07 19:34   ` Jain, Deepak K [this message]
2016-09-14  9:56 ` [dpdk-dev] [PATCH v2] " Deepak Kumar Jain
2016-09-19 16:37   ` [dpdk-dev] [PATCH v3] " Deepak Kumar Jain
2016-09-20  0:01     ` 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=A09C9DDE180C7E429EC68E2BFB95C9033942A08D@IRSMSX107.ger.corp.intel.com \
    --to=deepak.k.jain@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=john.griffin@intel.com \
    --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).