From: zhangfei <zhangfei.gao@linaro.org>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: jean-philippe <jean-philippe@linaro.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>,
francois.ozog@linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
ilias.apalodimas@linaro.org, iommu@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, Jerome Glisse <jglisse@redhat.com>,
grant.likely@arm.com,
"haojian . zhuang" <haojian.zhuang@linaro.org>,
linux-accelerators@lists.ozlabs.org,
linux-crypto@vger.kernel.org, guodong.xu@linaro.org,
kenneth-lee-2012@foxmail.com
Subject: Re: [PATCH v10 4/4] crypto: hisilicon - register zip engine to uacce
Date: Fri, 10 Jan 2020 15:07:08 +0800 [thread overview]
Message-ID: <8d35168e-ff68-1bb9-20e1-6bbac5afde00@linaro.org> (raw)
In-Reply-To: <20200109174859.00004b7b@Huawei.com>
On 2020/1/10 上午1:48, Jonathan Cameron wrote:
> On Mon, 16 Dec 2019 11:08:17 +0800
> Zhangfei Gao <zhangfei.gao@linaro.org> wrote:
>
>> Register qm to uacce framework for user crypto driver
>>
>> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
>> Signed-off-by: Zhou Wang <wangzhou1@hisilicon.com>
> Very nice to see how minimal the changes are.
>
> Whilst uacce in general isn't crypto specific, as we are looking
> at changes in a crypto driver, this will need a crypto Ack.
>
> Herbert, this is about as non invasive as things can get and
> provide a user space shared virtual addressing based interface.
> What do you think?
>
> From my side, for what it's worth...
>
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Thanks Jonathan
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-01-10 7:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 3:08 [PATCH v10 0/4] Add uacce module for Accelerator Zhangfei Gao
2019-12-16 3:08 ` [PATCH v10 1/4] uacce: Add documents for uacce Zhangfei Gao
2019-12-16 3:08 ` [PATCH v10 2/4] uacce: add uacce driver Zhangfei Gao
2020-01-09 17:38 ` Jonathan Cameron
2020-01-10 6:55 ` zhangfei.gao
2020-01-10 10:10 ` Jonathan Cameron
2020-01-10 14:50 ` zhangfei.gao
2019-12-16 3:08 ` [PATCH v10 3/4] crypto: hisilicon - Remove module_param uacce_mode Zhangfei Gao
2020-01-09 17:40 ` Jonathan Cameron
2019-12-16 3:08 ` [PATCH v10 4/4] crypto: hisilicon - register zip engine to uacce Zhangfei Gao
2020-01-09 17:48 ` Jonathan Cameron
2020-01-10 7:07 ` zhangfei [this message]
2019-12-23 13:41 ` [PATCH v10 0/4] Add uacce module for Accelerator zhangfei
2020-01-08 16:47 ` Dave Jiang
2020-01-09 17:49 ` Jonathan Cameron
2020-01-10 7:03 ` zhangfei
2020-01-10 10:08 ` Jonathan Cameron
2020-01-10 11:29 ` zhangfei.gao
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=8d35168e-ff68-1bb9-20e1-6bbac5afde00@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=Jonathan.Cameron@Huawei.com \
--cc=arnd@arndb.de \
--cc=francois.ozog@linaro.org \
--cc=grant.likely@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=ilias.apalodimas@linaro.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=jglisse@redhat.com \
--cc=kenneth-lee-2012@foxmail.com \
--cc=linux-accelerators@lists.ozlabs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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