Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Wei Yongjun <weiyj.lk@gmail.com>, Matt Mackall <mpm@selenic.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Wenyou Yang <wenyou.yang@atmel.com>
Cc: Wei Yongjun <weiyongjun1@huawei.com>, <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH -next] hwrng: atmel - use clk_disable_unprepare instead of clk_disable
Date: Mon, 14 Nov 2016 09:02:28 +0100	[thread overview]
Message-ID: <b8d6676b-127b-804e-0d77-e4defcdfdff2@atmel.com> (raw)
In-Reply-To: <1478876207-29820-1-git-send-email-weiyj.lk@gmail.com>

Le 11/11/2016 à 15:56, Wei Yongjun a écrit :
> From: Wei Yongjun <weiyongjun1@huawei.com>
> 
> Since clk_prepare_enable() is used to get trng->clk, we should
> use clk_disable_unprepare() to release it for the error path.
> 
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>

Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>

Thank you.

Best regards,

> ---
>  drivers/char/hw_random/atmel-rng.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/char/hw_random/atmel-rng.c b/drivers/char/hw_random/atmel-rng.c
> index ae7cae5..661c82c 100644
> --- a/drivers/char/hw_random/atmel-rng.c
> +++ b/drivers/char/hw_random/atmel-rng.c
> @@ -94,7 +94,7 @@ static int atmel_trng_probe(struct platform_device *pdev)
>  	return 0;
>  
>  err_register:
> -	clk_disable(trng->clk);
> +	clk_disable_unprepare(trng->clk);
>  	return ret;
>  }
> 
> 


-- 
Nicolas Ferre

      reply	other threads:[~2016-11-14  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 14:56 [PATCH -next] hwrng: atmel - use clk_disable_unprepare instead of clk_disable Wei Yongjun
2016-11-14  8:02 ` Nicolas Ferre [this message]

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=b8d6676b-127b-804e-0d77-e4defcdfdff2@atmel.com \
    --to=nicolas.ferre@atmel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=weiyj.lk@gmail.com \
    --cc=weiyongjun1@huawei.com \
    --cc=wenyou.yang@atmel.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