public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: LeoLiu-oc <LeoLiu-oc@zhaoxin.com>
Cc: olivia@selenic.com, martin@kaiser.cx, jiajie.ho@starfivetech.com,
	jenny.zhang@starfivetech.com, mmyangfl@gmail.com,
	robh@kernel.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org, x86@vger.kernel.org,
	CobeChen@zhaoxin.com, TonyWWang@zhaoxin.com, YunShen@zhaoxin.com,
	LeoLiu@zhaoxin.com
Subject: Re: [PATCH v2] hwrng: add Zhaoxin rng driver base on rep_xstore instruction
Date: Fri, 1 Dec 2023 17:31:07 +0800	[thread overview]
Message-ID: <ZWmn2yDENnSjew4t@gondor.apana.org.au> (raw)
In-Reply-To: <20231121032939.610048-1-LeoLiu-oc@zhaoxin.com>

On Tue, Nov 21, 2023 at 11:29:39AM +0800, LeoLiu-oc wrote:
>
> +config HW_RANDOM_ZHAOXIN
> +	tristate "Zhaoxin HW Random Number Generator support"
> +	depends on X86
> +	default HW_RANDOM

Please remove this default.

> diff --git a/drivers/char/hw_random/via-rng.c b/drivers/char/hw_random/via-rng.c
> index a9a0a3b09c8b..6d1312845802 100644
> --- a/drivers/char/hw_random/via-rng.c
> +++ b/drivers/char/hw_random/via-rng.c
> @@ -35,9 +35,6 @@
>  #include <asm/cpufeature.h>
>  #include <asm/fpu/api.h>
>  
> -
> -
> -

Please don't make unrelated changes in a patch.

>  	pr_info("VIA RNG detected\n");
>  	err = hwrng_register(&via_rng);
>  	if (err) {
> -		pr_err(PFX "RNG registering failed (%d)\n",
> -		       err);
> +		pr_err(PFX "RNG registering failed (%d)\n", err);

Ditto.

> +#include <crypto/padlock.h>
> +#include <linux/module.h>
> +#include <linux/kernel.h>
> +#include <linux/hw_random.h>
> +#include <linux/delay.h>
> +#include <linux/io.h>
> +#include <linux/cpufeature.h>
> +#include <asm/cpu_device_id.h>
> +#include <asm/fpu/api.h>

Please sort this alphabetically.

Thanks,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

  reply	other threads:[~2023-12-01  9:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07  7:09 [PATCH] hwrng: add Zhaoxin rng driver base on rep_xstore instruction LeoLiu-oc
2023-11-07 16:29 ` kernel test robot
2023-11-08  7:34 ` [PATCH v2] " LeoLiu-oc
2023-11-17 10:35   ` Herbert Xu
2023-11-17 11:19     ` LeoLiu-oc
2023-11-21  3:29 ` LeoLiu-oc
2023-12-01  9:31   ` Herbert Xu [this message]
2023-12-05  3:41     ` LeoLiu-oc
2023-12-01  9:34   ` Herbert Xu
2023-12-05  3:47     ` LeoLiu-oc
2023-12-01  9:38   ` Herbert Xu
2023-12-05  6:56     ` LeoLiu-oc
2023-12-21  6:26 ` [PATCH v3] " LeoLiu-oc
2023-12-23  0:11   ` kernel test robot
2023-12-23  0:21   ` kernel test robot
2023-12-23  7:04   ` kernel test robot
2023-12-25  2:53 ` [PATCH v4] " LeoLiu-oc
2023-12-26  0:54   ` kernel test robot
2023-12-26  1:04   ` kernel test robot
2023-12-26  7:49   ` kernel test robot
2023-12-27  3:58 ` [PATCH v5] " LeoLiu-oc

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=ZWmn2yDENnSjew4t@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=CobeChen@zhaoxin.com \
    --cc=LeoLiu-oc@zhaoxin.com \
    --cc=LeoLiu@zhaoxin.com \
    --cc=TonyWWang@zhaoxin.com \
    --cc=YunShen@zhaoxin.com \
    --cc=jenny.zhang@starfivetech.com \
    --cc=jiajie.ho@starfivetech.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@kaiser.cx \
    --cc=mmyangfl@gmail.com \
    --cc=olivia@selenic.com \
    --cc=robh@kernel.org \
    --cc=x86@vger.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