From: Stephan Mueller <smueller@chronox.de>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: linux-crypto@vger.kernel.org, linuxarm@huawei.com,
xuzaibo@huawei.com, Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Xiongfeng Wang <xiongfeng.wang@linaro.org>
Subject: Re: [RFC PATCH 2/3] crypto: hisilicon hacv1 driver
Date: Mon, 05 Feb 2018 15:10:59 +0100 [thread overview]
Message-ID: <25300210.7qS7PduyPT@tauon.chronox.de> (raw)
In-Reply-To: <20180205140203.00007e46@huawei.com>
Am Montag, 5. Februar 2018, 15:02:03 CET schrieb Jonathan Cameron:
Hi Jonathan,
> I could drop this for the initial submission and bring it in as an
> optimization with supporting numbers as a follow up patch.
I am not disputing the code itself. It just occurred to me that the code is
similar to the fixed code which did not handle an SGL with a leading SG entry
having no associated page. Thus, I thought I ask :-)
Ciao
Stephan
next prev parent reply other threads:[~2018-02-05 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 15:29 [RFC PATCH 0/3] Hisilicon SEC accelerator driver Jonathan Cameron
2018-01-30 15:29 ` [RFC PATCH 1/3] dt-bindings: Add bindings for Hisilicon SEC crypto accelerators Jonathan Cameron
[not found] ` <20180130152953.14068-2-jonathan.cameron-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-02-05 6:07 ` Rob Herring
2018-01-30 15:29 ` [RFC PATCH 2/3] crypto: hisilicon hacv1 driver Jonathan Cameron
[not found] ` <20180130152953.14068-3-jonathan.cameron-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-02-03 11:16 ` Stephan Müller
2018-02-05 14:02 ` Jonathan Cameron
2018-02-05 14:10 ` Stephan Mueller [this message]
[not found] ` <20180130152953.14068-1-jonathan.cameron-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-30 15:29 ` [RFC PATCH 3/3] arm64: dts: hisi: add SEC crypto accelerator nodes for hip07 SoC Jonathan Cameron
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=25300210.7qS7PduyPT@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=xiongfeng.wang@linaro.org \
--cc=xuzaibo@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