From: Gagandeep Singh <G.Singh@nxp.com>
To: wangyunjian <wangyunjian@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
"jerry.lilijun@huawei.com" <jerry.lilijun@huawei.com>,
"xudingke@huawei.com" <xudingke@huawei.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] fixes for caam_jr
Date: Fri, 15 May 2020 06:48:49 +0000 [thread overview]
Message-ID: <VI1PR04MB6960A0C23F677171386BC3F4E1BD0@VI1PR04MB6960.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1589453983-13188-1-git-send-email-wangyunjian@huawei.com>
> -----Original Message-----
> From: wangyunjian <wangyunjian@huawei.com>
> Sent: Thursday, May 14, 2020 4:30 PM
> To: dev@dpdk.org
> Cc: Gagandeep Singh <G.Singh@nxp.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; jerry.lilijun@huawei.com;
> xudingke@huawei.com; Yunjian Wang <wangyunjian@huawei.com>
> Subject: [dpdk-dev] [PATCH v3 0/2] fixes for caam_jr
>
> From: Yunjian Wang <wangyunjian@huawei.com>
>
> This series include two fixes patches for caam_jr driver.
>
> ---
> v3:
> * Add function to initialize g_uio_job_ring and g_job_rings
> * Add fix return type
> v2:
> * Change "job_ring->uio_fd" type suggested by Gagandeep Singh
>
> Yunjian Wang (2):
> crypto/caam_jr: fix wrong check of fd
> crypto/caam_jr: fix the functions to use the correct type
>
Series-acked-by: Gagandeep Singh <G.singh@nxp.com>
> drivers/crypto/caam_jr/caam_jr.c | 23 ++++++++++---
> drivers/crypto/caam_jr/caam_jr_hw_specific.h | 2 +-
> drivers/crypto/caam_jr/caam_jr_pvt.h | 9 +++---
> drivers/crypto/caam_jr/caam_jr_uio.c | 34 +++++++++++++-------
> 4 files changed, 47 insertions(+), 21 deletions(-)
>
> --
> 2.19.1
>
next prev parent reply other threads:[~2020-05-15 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 10:59 wangyunjian
2020-05-15 6:48 ` Gagandeep Singh [this message]
2020-05-17 14:10 ` 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=VI1PR04MB6960A0C23F677171386BC3F4E1BD0@VI1PR04MB6960.eurprd04.prod.outlook.com \
--to=g.singh@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerry.lilijun@huawei.com \
--cc=wangyunjian@huawei.com \
--cc=xudingke@huawei.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).