From: Bruno Wolff III <bruno@wolff.to>
To: Aaron Jones <aaronmdjones@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard not building on pre-rc1 4.19 kernels (Fedora)
Date: Mon, 20 Aug 2018 10:19:15 -0500 [thread overview]
Message-ID: <20180820151915.GA25379@wolff.to> (raw)
In-Reply-To: <87586e5d-0ca0-8b93-70b7-340e600f8f1e@gmail.com>
On Mon, Aug 20, 2018 at 14:43:53 +0000,
Aaron Jones <aaronmdjones@gmail.com> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA512
>
>This will be because Jason's RNG patch landed in mainline, but the
>kernel version number won't get bumped (so compat.h can use it
>properly) until 4.19 is released.
Thanks. That was enough information to tell me what to do to get it to
work with a temporary hack. I'm using a successful build as I type this.
next prev parent reply other threads:[~2018-08-20 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 4:40 Wireguard not building on pre-rc1 4.19 kernels (Fedora) Bruno Wolff III
2018-08-20 14:43 ` Aaron Jones
2018-08-20 15:19 ` Bruno Wolff III [this message]
2018-08-24 20:11 ` Bruno Wolff III
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=20180820151915.GA25379@wolff.to \
--to=bruno@wolff.to \
--cc=aaronmdjones@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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).