From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: "kernelci.org bot" <bot@kernelci.org>,
linux-next@vger.kernel.org, David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: next/master build: 214 builds: 10 failed, 204 passed, 17 errors, 57 warnings (next-20191210)
Date: Wed, 11 Dec 2019 10:24:55 +1100 [thread overview]
Message-ID: <20191211102455.7b55218e@canb.auug.org.au> (raw)
In-Reply-To: <5def8fc0.1c69fb81.d0c08.f4f4@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
Hi all,
On Tue, 10 Dec 2019 04:29:52 -0800 (PST) "kernelci.org bot" <bot@kernelci.org> wrote:
>
> allmodconfig (arm, gcc-8) — FAIL, 2 errors, 20 warnings, 0 section mismatches
>
> Errors:
> ERROR: "curve25519_base_arch" [drivers/net/wireguard/wireguard.ko] undefined!
curve25519_base_arch() is only defined for X86. Though its use is
restricted to CONFIG_CRYPTO_ARCH_HAVE_LIB_CURVE25519 being enabled.
Arm selects this if CRYPTO_CURVE25519_NEON is enabled (which it
probably is for an allmodconfig build).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-12-10 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 12:29 next/master build: 214 builds: 10 failed, 204 passed, 17 errors, 57 warnings (next-20191210) kernelci.org bot
2019-12-10 23:24 ` Stephen Rothwell [this message]
2019-12-11 9:26 ` [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function Jason A. Donenfeld
2019-12-11 9:26 ` [PATCH 2/2] crypto: curve25519 - re-add selftests Jason A. Donenfeld
2019-12-11 9:38 ` [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function Ard Biesheuvel
2019-12-11 9:40 ` Jason A. Donenfeld
2019-12-11 12:07 ` Jason A. Donenfeld
2019-12-12 6:08 ` Herbert Xu
2019-12-12 6:08 ` Herbert Xu
2019-12-10 23:26 ` next/master build: 214 builds: 10 failed, 204 passed, 17 errors, 57 warnings (next-20191210) Stephen Rothwell
2019-12-10 23:28 ` 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=20191211102455.7b55218e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Jason@zx2c4.com \
--cc=bot@kernelci.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.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 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.