public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: LeoLiu-oc <leoliu-oc@zhaoxin.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
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>,
	<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, 17 Nov 2023 19:19:19 +0800	[thread overview]
Message-ID: <88075c49-8118-4c4b-a2ce-e460180fa30c@zhaoxin.com> (raw)
In-Reply-To: <ZVdB7ZyjLay61mLp@gondor.apana.org.au>



在 2023/11/17 18:35, Herbert Xu 写道:
> On Wed, Nov 08, 2023 at 03:34:54PM +0800, LeoLiu-oc wrote:
>> From: LeoLiuoc <LeoLiu-oc@zhaoxin.com>
>>
>> Add support for Zhaoxin hardware random number generator.
>> This driver base on rep_xstore instruction and uses the same
>> X86_FEATURE_XSTORE as via-rng driver. Therefore, modify the x86_cpu_id
>> array in the via-rng driver, so that the corresponding driver can be
>> correctly loader on respective platforms.
>>
>> ---
>>
>> v1 -> v2:
>> 1. Fix assembler code errors
>> 2. Remove redundant CPU model check codes
>>
>> Signed-off-by: LeoLiuoc <LeoLiu-oc@zhaoxin.com>
>> ---
>>   drivers/char/hw_random/Kconfig       | 13 ++++
>>   drivers/char/hw_random/Makefile      |  1 +
>>   drivers/char/hw_random/via-rng.c     | 23 +++----
>>   drivers/char/hw_random/zhaoxin-rng.c | 95 ++++++++++++++++++++++++++++
>>   4 files changed, 119 insertions(+), 13 deletions(-)
>>   create mode 100644 drivers/char/hw_random/zhaoxin-rng.c
> 
> Please cc x86@vger.kernel.org as the same comments to the other
> zhaoxin driver seems to be applicable here.
> 
> Thanks,

Okay, Will re-send v2 add cc x86@vger.kernel.org.


Best Regards
Leoliu-oc


  reply	other threads:[~2023-11-17 11:19 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 [this message]
2023-11-21  3:29 ` LeoLiu-oc
2023-12-01  9:31   ` Herbert Xu
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=88075c49-8118-4c4b-a2ce-e460180fa30c@zhaoxin.com \
    --to=leoliu-oc@zhaoxin.com \
    --cc=CobeChen@zhaoxin.com \
    --cc=LeoLiu@zhaoxin.com \
    --cc=TonyWWang@zhaoxin.com \
    --cc=YunShen@zhaoxin.com \
    --cc=herbert@gondor.apana.org.au \
    --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 \
    /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