From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pinebookpro-kernel: fix build w/ gcc10
Date: Sat, 05 Sep 2020 22:23:48 +0200 [thread overview]
Message-ID: <20200905202348.Fj3LlAWcbxG0LoPHVKN4Xd_zfFQ4NfP0WwmIrZ3IZfo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24699@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/24699#issuecomment-687658249
Comment:
I think other kernels have the same function so that would apply there too.
I'd have to try and build all of them for aarch64 to tell which ones need that same patch.
Of course just inspecting the `crypto_aegis128_init_neon` function in `crypto/aegis128-neon-inner.c` in other kernels should tell that as well. OTOH I believe kernels will sooner or later have this fixed for gcc10 anyway.
Edit: I already built 5.7.17 for aarch64{,-musl} so there it does not seem to be required.
5.8.5 did build for aarch64-musl, update to 5.8.6 is pending.
next prev parent reply other threads:[~2020-09-05 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 17:22 [PR PATCH] " pullmoll
2020-09-05 19:21 ` ericonr
2020-09-05 19:51 ` CameronNemo
2020-09-05 20:19 ` pullmoll
2020-09-05 20:23 ` pullmoll [this message]
2020-09-05 20:42 ` pullmoll
2020-09-05 23:58 ` pullmoll
2020-09-06 0:05 ` q66
2020-09-06 0:12 ` q66
2020-09-06 0:13 ` q66
2020-09-22 21:19 ` [PR PATCH] [Closed]: " pullmoll
2020-09-30 1:01 ` CameronNemo
2020-09-30 6:10 ` pullmoll
2020-09-30 6:36 ` CameronNemo
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=20200905202348.Fj3LlAWcbxG0LoPHVKN4Xd_zfFQ4NfP0WwmIrZ3IZfo@z \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 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).