From: Marek Vasut <marex@denx.de>
To: Sonic Zhang <sonic.adi@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org,
adi-buildroot-devel@lists.sourceforge.net,
Sonic Zhang <sonic.zhang@analog.com>
Subject: Re: [PATCH 1/2] crypto: bfin_crc: ignore duplicated registration of the same algorithm
Date: Thu, 10 Apr 2014 10:59:21 +0200 [thread overview]
Message-ID: <201404101059.21811.marex@denx.de> (raw)
In-Reply-To: <1397119259-20638-1-git-send-email-sonic.adi@gmail.com>
On Thursday, April 10, 2014 at 10:40:58 AM, Sonic Zhang wrote:
> From: Sonic Zhang <sonic.zhang@analog.com>
>
> in case of multiple crc devices are probed.
>
> Signed-off-by: Sonic Zhang <sonic.zhang@analog.com>
> ---
> drivers/crypto/bfin_crc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/bfin_crc.c b/drivers/crypto/bfin_crc.c
> index cea3e8c..5f5f427 100644
> --- a/drivers/crypto/bfin_crc.c
> +++ b/drivers/crypto/bfin_crc.c
> @@ -672,7 +672,7 @@ static int bfin_crypto_crc_probe(struct platform_device
> *pdev) platform_set_drvdata(pdev, crc);
Rant: Reading through the code a little, the platform_set_drvdata() should
happen before you add the new CRC device into the list (above this code).
> ret = crypto_register_ahash(&algs);
> - if (ret) {
> + if (ret && ret != -EEXIST) {
Uh oh, how is this supposed to work ? Does blackfin have multiple crc32
processing units ? Can you simply not check if the crc_list is not empty and
avoid calling crypto_register_ahash() for subsequent crc32 units at all ?
> spin_lock(&crc_list.lock);
> list_del(&crc->list);
> spin_unlock(&crc_list.lock);
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-10 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 8:40 [PATCH 1/2] crypto: bfin_crc: ignore duplicated registration of the same algorithm Sonic Zhang
2014-04-10 8:40 ` [PATCH 2/2] crypto: bfin_crc: avoid get physical address of coherence memory by dma_map_single Sonic Zhang
2014-04-10 9:02 ` Marek Vasut
2014-04-14 4:41 ` Sonic Zhang
2014-04-10 8:59 ` Marek Vasut [this message]
2014-04-10 9:51 ` [PATCH 1/2] crypto: bfin_crc: ignore duplicated registration of the same algorithm Sonic Zhang
2014-04-10 12:33 ` Marek Vasut
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=201404101059.21811.marex@denx.de \
--to=marex@denx.de \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=sonic.adi@gmail.com \
--cc=sonic.zhang@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.