From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"O Mahony, Billy" <billy.o.mahony@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"O Mahony, Billy" <billy.o.mahony@intel.com>
Subject: Re: [dpdk-dev] [PATCH] comment: Describe how rte_cryptodev_info_get returns capabilities
Date: Wed, 25 Oct 2017 16:13:22 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CC3CF28@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435892B1860@IRSMSX101.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Trahe, Fiona
> Sent: Wednesday, October 25, 2017 5:02 PM
> To: O Mahony, Billy <billy.o.mahony@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Cc: dev@dpdk.org; O Mahony, Billy <billy.o.mahony@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] comment: Describe how
> rte_cryptodev_info_get returns capabilities
>
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Billy O'Mahony
> > Sent: Tuesday, October 24, 2017 3:53 PM
> > To: Doherty, Declan <declan.doherty@intel.com>
> > Cc: dev@dpdk.org; O Mahony, Billy <billy.o.mahony@intel.com>
> > Subject: [dpdk-dev] [PATCH] comment: Describe how
> rte_cryptodev_info_get returns capabilities
> >
> > Signed-off-by: Billy O'Mahony <billy.o.mahony@intel.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
Modified to the title to "cryptodev: extend info get function documentation",
and added a small description in the commit message.
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-10-25 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 14:53 Billy O'Mahony
2017-10-25 16:01 ` Trahe, Fiona
2017-10-25 16:13 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8976CC3CF28@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=billy.o.mahony@intel.com \
--cc=declan.doherty@intel.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).