From: Akhil Goyal <akhil.goyal@nxp.com>
To: Gagandeep Singh <G.Singh@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/caam_jr: fix the shared desc endianness
Date: Tue, 9 Apr 2019 14:17:35 +0000 [thread overview]
Message-ID: <VI1PR04MB48936B907E93876944279D78E62D0@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
Message-ID: <20190409141735.3XFexXGeBnNvHo3pDKfeJsISlPaovGlG-Kid9DrB8E8@z> (raw)
In-Reply-To: <1554736925-13184-1-git-send-email-g.singh@nxp.com>
> -----Original Message-----
> From: Gagandeep Singh
> Sent: Monday, April 8, 2019 2:29 PM
> To: dev@dpdk.org; Akhil Goyal <akhil.goyal@nxp.com>
> Cc: Gagandeep Singh <G.Singh@nxp.com>
> Subject: [PATCH 1/2] crypto/caam_jr: fix the shared desc endianness
>
> build a shared descriptor accordingly if core and
> CAAM endianness is same or different
>
> Fixes: 6ef6beca8844 ("crypto/caam_jr: add enqueue/dequeue operations")
> Cc: g.singh@nxp.com
>
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2019-04-09 14:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 8:59 Gagandeep Singh
2019-04-08 8:59 ` Gagandeep Singh
2019-04-08 8:59 ` [dpdk-dev] [PATCH 2/2] crypto/caam_jr: fix total length in AUTH only sg case Gagandeep Singh
2019-04-08 8:59 ` Gagandeep Singh
2019-04-09 14:06 ` Akhil Goyal
2019-04-09 14:06 ` Akhil Goyal
2019-04-09 14:17 ` Akhil Goyal [this message]
2019-04-09 14:17 ` [dpdk-dev] [PATCH 1/2] crypto/caam_jr: fix the shared desc endianness Akhil Goyal
2019-04-16 14:51 ` Akhil Goyal
2019-04-16 14:51 ` Akhil Goyal
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=VI1PR04MB48936B907E93876944279D78E62D0@VI1PR04MB4893.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=G.Singh@nxp.com \
--cc=dev@dpdk.org \
/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).