linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: zain wang <wzz@rock-chips.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Heiko Stuebner <heiko@sntech.de>
Cc: jekarlson@gmail.com, shawn.lin@rock-chips.com,
	linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	zain wang <wzz@rock-chips.com>
Subject: [RESEND PATCH 0/2] crypto/rockchip: fix some issue which causes crypto failed
Date: Mon, 24 Jul 2017 09:23:12 +0800	[thread overview]
Message-ID: <1500859394-1799-1-git-send-email-wzz@rock-chips.com> (raw)

These patches fix some bugs on rockchip's crypto which would cause crypto failed.

zain wang (2):
  crypto: rockchip - move the crypto completion from interrupt context
  crypto: rockchip - return the err code when unable dequeue the crypto
    request

 drivers/crypto/rockchip/rk3288_crypto.c            | 58 +++++++++++-----------
 drivers/crypto/rockchip/rk3288_crypto.h            |  4 +-
 drivers/crypto/rockchip/rk3288_crypto_ablkcipher.c | 17 ++++++-
 drivers/crypto/rockchip/rk3288_crypto_ahash.c      | 16 +++++-
 4 files changed, 62 insertions(+), 33 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-07-24  1:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  1:23 zain wang [this message]
2017-07-24  1:23 ` [RESEND PATCH 1/2] crypto: rockchip - move the crypto completion from interrupt context zain wang
2017-07-24  1:23 ` [RESEND PATCH 2/2] crypto: rockchip - return the err code when unable dequeue the crypto request zain wang
2017-07-26 17:44 ` [RESEND PATCH 0/2] crypto/rockchip: fix some issue which causes crypto failed Emil Karlson
2017-08-03  6:26 ` Herbert Xu

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=1500859394-1799-1-git-send-email-wzz@rock-chips.com \
    --to=wzz@rock-chips.com \
    --cc=davem@davemloft.net \
    --cc=heiko@sntech.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=jekarlson@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.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).