From: Herbert Xu <herbert@gondor.apana.org.au>
To: Zhou Wang <wangzhou1@hisilicon.com>
Cc: linux-kernel@vger.kernel.org, linuxarm@huawei.com,
linux-crypto@vger.kernel.org,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH 3/4] crypto: hisilicon: Add HiSilicon ZIP accelerator support
Date: Fri, 18 Jan 2019 18:09:26 +0800 [thread overview]
Message-ID: <20190118100926.tr6yti2vlqbnwnd4@gondor.apana.org.au> (raw)
In-Reply-To: <5C418659.30904@hisilicon.com>
On Fri, Jan 18, 2019 at 03:55:05PM +0800, Zhou Wang wrote:
>
> However, another question is that seems other subsystems in kernel,
> e.g. zswap still use crypto_alloc_comp. So we'd better register this
> ZIP engine using both cryto_alloc_comp and scomp/acomp interface to
> make it compatible with other subsystems?
Existing users should switch over to acomp. We're not adding any
more new algorithms to the legacy compress interface.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2019-01-18 10:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 7:51 [PATCH 0/4] crypto: hisilicon: Add HiSilicon QM and ZIP controller driver Zhou Wang
2018-12-22 7:51 ` [PATCH 1/4] Documentation: Add debugfs doc for hisi_zip Zhou Wang
2018-12-22 7:51 ` [PATCH 2/4] crypto: hisilicon: Add queue management driver for HiSilicon QM module Zhou Wang
2018-12-22 7:51 ` [PATCH 3/4] crypto: hisilicon: Add HiSilicon ZIP accelerator support Zhou Wang
2019-01-11 6:08 ` Herbert Xu
2019-01-11 6:34 ` Zhou Wang
2019-01-16 14:12 ` Zhou Wang
2019-01-18 4:55 ` Herbert Xu
2019-01-18 7:55 ` Zhou Wang
2019-01-18 10:09 ` Herbert Xu [this message]
2018-12-22 7:51 ` [PATCH 4/4] MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver Zhou Wang
2019-01-10 6:30 ` [PATCH 0/4] crypto: hisilicon: Add " Zhou Wang
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=20190118100926.tr6yti2vlqbnwnd4@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=wangzhou1@hisilicon.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).