All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Theodore Ts'o <tytso@mit.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the random tree
Date: Mon, 31 Oct 2022 11:31:10 +0100	[thread overview]
Message-ID: <Y1+j7jOV8fYMGXiD@zx2c4.com> (raw)
In-Reply-To: <20221031170956.2cdf101a@canb.auug.org.au>

On Mon, Oct 31, 2022 at 05:09:56PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the random tree, today's linux-next build (arm64 defconfig)
> failed like this:
> 
> arch/arm64/kernel/pi/kaslr_early.c: In function 'kaslr_early_init':
> arch/arm64/kernel/pi/kaslr_early.c:97:22: error: implicit declaration of function '__early_cpu_has_rndr' [-Werror=implicit-function-declaration]
>    97 |                 if (!__early_cpu_has_rndr() ||
>       |                      ^~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
> 
> Caused by commit
> 
>   70ae866ab6b3 ("random: remove early archrandom abstraction")
> 
> I have used the ramdom tree from next-20221028 for today.

Thanks, sorted.

Jason

  reply	other threads:[~2022-10-31 10:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31  6:09 linux-next: build failure after merge of the random tree Stephen Rothwell
2022-10-31 10:31 ` Jason A. Donenfeld [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-10-01 15:40 Mark Brown
2026-10-01 19:30 ` Nathan Chancellor
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-12-13  3:36 Stephen Rothwell
2022-12-13  4:02 ` 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=Y1+j7jOV8fYMGXiD@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.