From: Akhil Goyal <gakhil@marvell.com>
To: David Marchand <david.marchand@redhat.com>,
"Wang, Songyi" <songyi.wang@intel.com>,
Fan Zhang <fanzhang.oss@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Dong, Yao" <yao.dong@intel.com>
Subject: RE: [EXT] Re: Comments/Doc error for CRYPTODEV of DPDK
Date: Fri, 19 Jan 2024 08:08:29 +0000 [thread overview]
Message-ID: <CO6PR18MB448446E083FA7960CD9B93F6D8702@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8zs1Mhad53V24gH+AY487uO0VfBx+yJ3qae-nV9eeBXMA@mail.gmail.com>
Hi,
> Hello,
>
> On Fri, Jan 19, 2024 at 8:48 AM Wang, Songyi <songyi.wang@intel.com> wrote:
> >
> > Hi maintainer of DPDK,
>
> Redirecting to the cryptodev maintainers.
> Akhil, Fan, can you have a look?
>
> Thanks.
>
> >
> >
> >
> > I’ve noticed an error on comment of DPDK version 23.11 rte_cryptodev.h: 928-
> 930
>
Can you specify the error?
Regards,
Akhil
next prev parent reply other threads:[~2024-01-19 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 8:58 Wang, Songyi
2024-01-19 7:51 ` David Marchand
2024-01-19 8:08 ` Akhil Goyal [this message]
2024-01-19 8:27 ` [EXT] " Akhil Goyal
2024-01-19 8:32 ` Wang, Songyi
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=CO6PR18MB448446E083FA7960CD9B93F6D8702@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=songyi.wang@intel.com \
--cc=yao.dong@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).