From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Verma, Shally" <Shally.Verma@cavium.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Gupta, Ashish" <Ashish.Gupta@cavium.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] compressdev: clarify mbuf offsets
Date: Tue, 22 May 2018 12:45:16 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CD10EF4@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <MWHPR0701MB364102E2848C005ED2968DD7F0940@MWHPR0701MB3641.namprd07.prod.outlook.com>
> -----Original Message-----
> From: Verma, Shally [mailto:Shally.Verma@cavium.com]
> Sent: Tuesday, May 22, 2018 12:41 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Trahe, Fiona
> <fiona.trahe@intel.com>; Gupta, Ashish <Ashish.Gupta@cavium.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] compressdev: clarify mbuf offsets
>
>
>
> >-----Original Message-----
> >From: Pablo de Lara [mailto:pablo.de.lara.guarch@intel.com]
> >Sent: 22 May 2018 16:25
> >To: fiona.trahe@intel.com; Gupta, Ashish <Ashish.Gupta@cavium.com>;
> >Verma, Shally <Shally.Verma@cavium.com>
> >Cc: dev@dpdk.org; Pablo de Lara <pablo.de.lara.guarch@intel.com>
> >Subject: [PATCH] compressdev: clarify mbuf offsets
> >
> >Add extra clarification about offset in source and destination mbuf
> >used in compressdev, when they are a chain of mbufs.
> >
> >Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> >---
> Reviewed-by: Shally Verma <shally.verma@caviumnetworks.com>
>
Applied to dpdk-next-crypto.
Thanks,
Pablo
next prev parent reply other threads:[~2018-05-22 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 10:54 Pablo de Lara
2018-05-22 11:40 ` Verma, Shally
2018-05-22 12:45 ` De Lara Guarch, Pablo [this message]
2018-05-22 12:58 ` Trahe, Fiona
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=E115CCD9D858EF4F90C690B0DCB4D8976CD10EF4@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=Ashish.Gupta@cavium.com \
--cc=Shally.Verma@cavium.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@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).