From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Theodore Ts'o <tytso@mit•edu>, "Jason A. Donenfeld" <Jason@zx2c4•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the random tree
Date: Tue, 13 Dec 2022 14:36:22 +1100 [thread overview]
Message-ID: <20221213143622.5b2cde33@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
Hi all,
After merging the random tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/char/hw_random/powernv-rng.c: In function 'powernv_rng_read':
drivers/char/hw_random/powernv-rng.c:26:17: error: implicit declaration of function 'pnv_get_random_long'; did you mean 'get_random_long'? [-Werror=implicit-function-declaration]
26 | pnv_get_random_long(buf++);
| ^~~~~~~~~~~~~~~~~~~
| get_random_long
net/ipv4/tcp_plb.c: In function 'tcp_plb_update_state_upon_rto':
net/ipv4/tcp_plb.c:100:18: error: implicit declaration of function 'prandom_u32_max'; did you mean 'prandom_u32_state'? [-Werror=implicit-function-declaration]
100 | pause += prandom_u32_max(pause);
| ^~~~~~~~~~~~~~~
| prandom_u32_state
The latter call has been added recently, but the former is presumably
caused by commit
5d1056fb3dd8 ("random: do not include <asm/archrandom.h> from random.h")
I have used the random tree from next-20221208 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-12-13 3:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 3:36 Stephen Rothwell [this message]
2022-12-13 4:02 ` linux-next: build failure after merge of the random tree Jason A. Donenfeld
-- strict thread matches above, loose matches on Subject: below --
2026-01-23 21:48 Mark Brown
2026-01-23 21:56 ` Andy Shevchenko
2026-01-23 22:10 ` Mark Brown
2026-01-23 22:18 ` Andy Shevchenko
2026-01-23 22:22 ` Mark Brown
2026-01-23 22:44 ` Andy Shevchenko
2026-02-02 15:22 ` Mark Brown
2026-02-02 17:34 ` Andy Shevchenko
2026-02-02 19:51 ` Jason A. Donenfeld
2024-10-01 3:44 Stephen Rothwell
2024-10-01 8:06 ` Uros Bizjak
2024-10-10 4:38 ` Stephen Rothwell
2024-11-20 2:34 ` Stephen Rothwell
2024-09-05 10:19 Stephen Rothwell
2024-09-05 12:47 ` Jason A. Donenfeld
2024-03-25 1:01 Stephen Rothwell
2024-03-26 16:08 ` Jason A. Donenfeld
2022-12-14 1:53 Stephen Rothwell
2022-12-14 5:37 ` Jason A. Donenfeld
2022-10-31 6:09 Stephen Rothwell
2022-10-31 10:31 ` Jason A. Donenfeld
2022-10-24 2:23 Stephen Rothwell
2022-10-24 4:28 ` Jason A. Donenfeld
2022-10-24 6:33 ` Stephen Rothwell
2022-03-03 8:04 Stephen Rothwell
2022-03-03 10:41 ` Jason A. Donenfeld
2018-06-29 6:06 Stephen Rothwell
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=20221213143622.5b2cde33@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=Jason@zx2c4$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tytso@mit$(echo .)edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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