mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lars Persson <lars.persson@axis.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
	<robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<linux-crypto@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Cc: Rabin Vincent <rabinv@axis.com>
Subject: Re: [PATCH v4 2/4] crypto: add crypto_(un)register_ahashes()
Date: Thu, 10 Aug 2017 16:54:16 +0200	[thread overview]
Message-ID: <6d27d00b-cac9-d613-90ec-782815266b87@axis.com> (raw)
In-Reply-To: <01cfbf11707a9907d87c59fb47385c4178a08688.1502368677.git.larper@axis.com>



On 08/10/2017 02:53 PM, Lars Persson wrote:
> From: Rabin Vincent <rabinv@axis.com>
> 
> There are already helpers to (un)register multiple normal
> and AEAD algos.  Add one for ahashes too.
> 
> Signed-off-by: Lars Persson <larper@axis.com>
> Signed-off-by: Rabin Vincent <rabinv@axis.com>
> ---
> v4: crypto_register_skciphers was used where crypto_unregister_skciphers
>      was intended.
>

The v4 change comment above in fact belongs to patch 3/4 of this series. 
Sorry for the confusion.

BR,
  Lars

  reply	other threads:[~2017-08-10 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-10 12:53 [PATCH v4 0/4] crypto: add driver for Axis ARTPEC crypto accelerator Lars Persson
2017-08-10 12:53 ` [PATCH v4 1/4] dt-bindings: crypto: add ARTPEC crypto Lars Persson
2017-08-10 12:53 ` [PATCH v4 2/4] crypto: add crypto_(un)register_ahashes() Lars Persson
2017-08-10 14:54   ` Lars Persson [this message]
2017-08-10 12:53 ` [PATCH v4 3/4] crypto: axis: add ARTPEC-6/7 crypto accelerator driver Lars Persson
2017-08-10 12:53 ` [PATCH v4 4/4] MAINTAINERS: Add ARTPEC crypto maintainer Lars Persson
2017-08-22  7:57 ` [PATCH v4 0/4] crypto: add driver for Axis ARTPEC crypto accelerator 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=6d27d00b-cac9-d613-90ec-782815266b87@axis.com \
    --to=lars.persson@axis.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rabinv@axis.com \
    --cc=robh+dt@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

all inboxes | Powered by JetHome®