linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hadar Gat <Hadar.Gat@arm.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	nd <nd@arm.com>
Subject: RE: linux-next: Tree for Apr 17 (drivers/char/hw_random/cctrng.c)
Date: Fri, 17 Apr 2020 20:14:35 +0000	[thread overview]
Message-ID: <DB6PR0802MB2533F8342A00C8B9A9CB3547E9D90@DB6PR0802MB2533.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <d1786751-48de-e75c-44df-3edad4f21efb@infradead.org>

Hi Randy,
Thank you for reporting.
I will fix this issue shortly.
Hadar

> -----Original Message-----
> From: Randy Dunlap <rdunlap@infradead.org>
> Sent: Friday, 17 April 2020 18:23
> To: Stephen Rothwell <sfr@canb.auug.org.au>; Linux Next Mailing List
> <linux-next@vger.kernel.org>
> Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Linux Crypto
> Mailing List <linux-crypto@vger.kernel.org>; Hadar Gat
> <Hadar.Gat@arm.com>
> Subject: Re: linux-next: Tree for Apr 17 (drivers/char/hw_random/cctrng.c)
> 
> On 4/16/20 9:50 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20200416:
> >
> 
> 
> on i386:
> 
> ../drivers/char/hw_random/cctrng.c: In function
> ‘cc_trng_compwork_handler’:
> ../drivers/char/hw_random/cctrng.c:334:49: error: ‘fips_enabled’ undeclared
> (first use in this function); did you mean ‘nx_enabled’?
>   if (CC_REG_FLD_GET(RNG_ISR, CRNGT_ERR, isr) && fips_enabled) {
>                                                  ^~~~~~~~~~~~
>                                                  nx_enabled
> ../drivers/char/hw_random/cctrng.c:334:49: note: each undeclared identifier
> is reported only once for each function it appears in
> ../drivers/char/hw_random/cctrng.c:335:3: error: implicit declaration of
> function ‘fips_fail_notify’; did you mean ‘sysfs_notify’? [-Werror=implicit-
> function-declaration]
>    fips_fail_notify();
>    ^~~~~~~~~~~~~~~~
>    sysfs_notify
> 
> 
> Full randconfig file is attached.
> 
> --
> ~Randy
> Reported-by: Randy Dunlap <rdunlap@infradead.org>

      reply	other threads:[~2020-04-17 20:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17  4:50 linux-next: Tree for Apr 17 Stephen Rothwell
2020-04-17  6:16 ` linux-next: Tree for Apr 17 (pinctrl-mcp23s08) Randy Dunlap
2020-04-17 10:22   ` Linus Walleij
2020-04-17  7:19 ` linux-next: Tree for Apr 17 Christian Borntraeger
2020-04-17  7:27   ` Mauro Carvalho Chehab
2020-04-17 14:48 ` linux-next: Tree for Apr 17 (mmc/host/sdhci-of-at91.c) Randy Dunlap
2020-04-20  9:12   ` Ulf Hansson
2020-04-20 10:28     ` Adrian Hunter
2020-04-20 12:27       ` Masahiro Yamada
2020-04-20 13:45         ` Adrian Hunter
2020-04-22 10:15         ` Ulf Hansson
2020-04-22 10:54           ` Masahiro Yamada
2020-04-17 15:23 ` linux-next: Tree for Apr 17 (drivers/char/hw_random/cctrng.c) Randy Dunlap
2020-04-17 20:14   ` Hadar Gat [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=DB6PR0802MB2533F8342A00C8B9A9CB3547E9D90@DB6PR0802MB2533.eurprd08.prod.outlook.com \
    --to=hadar.gat@arm.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nd@arm.com \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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;
as well as URLs for NNTP newsgroup(s).