linux-kernel - Re: [PATCH v5] crypto: hisilicon/trng

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAAXyoMMBWnqQGVWVOsEaKviukQJK1iyx+OAez0AQfKPL5b_UvQ@mail.gmail.com>
Date:   Sun, 9 Apr 2023 00:06:06 +0800
From:   Yangfl <mmyangfl@...il.com>
To:     Herbert Xu <herbert@...dor.apana.org.au>
Cc:     linux-crypto@...r.kernel.org, Weili Qian <qianweili@...wei.com>,
        Zhou Wang <wangzhou1@...ilicon.com>,
        "David S. Miller" <davem@...emloft.net>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5] crypto: hisilicon/trng - add support for HiSTB TRNG

Herbert Xu <herbert@...dor.apana.org.au> 于2023年4月6日周四 16:53写道：
>
> On Sun, Apr 02, 2023 at 12:44:40AM +0800, David Yang wrote:
> > HiSTB TRNG are found on some HiSilicon STB SoCs.
> >
> > Signed-off-by: David Yang <mmyangfl@...il.com>
> > ---
> > v2: fix typo
> > v3: add option for post process depth, adjust timeout
> > v4: do not case to __iomem, as requested
> > v5: do not use rng->priv at all
> >  drivers/crypto/hisilicon/Kconfig         |   7 +
> >  drivers/crypto/hisilicon/Makefile        |   2 +-
> >  drivers/crypto/hisilicon/trng/Makefile   |   3 +
> >  drivers/crypto/hisilicon/trng/trng-stb.c | 176 +++++++++++++++++++++++
> >  4 files changed, 187 insertions(+), 1 deletion(-)
> >  create mode 100644 drivers/crypto/hisilicon/trng/trng-stb.c
>
> Patch applied.  Thanks.
> --
> Email: Herbert Xu <herbert@...dor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

Thanks for merging this patch. But after considering your former reply
about drivers/char/hw_random , I'm thinking if that is a better place
for this driver. If that is the case I'd like to post a new version of
patch.

Sorry for late reply.