From: Bruno Wolff III <bruno@wolff.to>
To: wireguard@lists.zx2c4.com
Subject: Re: Pre 5.1-rc1 build issue
Date: Wed, 13 Mar 2019 13:52:59 -0500 [thread overview]
Message-ID: <20190313185259.GA4579@wolff.to> (raw)
In-Reply-To: <20190313183818.GA4501@wolff.to>
On Wed, Mar 13, 2019 at 13:38:18 -0500,
Bruno Wolff III <bruno@wolff.to> wrote:
>Commit https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d2c5c103b1337f590b7edf1509a6e294bdf22402
>removed net/netfilter/nf_nat_core.h, which breaks wireguard builds for
>5.1.0-0.rc0.git5.2.fc31.x86_64.
>
>It sounds like it isn't needed any more from the commit message.
There are also some rcu changes that I just guessed on fixes for. I think
this change was covered in Paul McKenney's LCA talk in January.
I got something that seems to be working. So I'm good until the real fixes
are ready.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-03-13 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 18:38 Pre 5.1-rc1 build issue Bruno Wolff III
2019-03-13 18:52 ` Bruno Wolff III [this message]
2019-03-13 20:44 ` Jason A. Donenfeld
2019-03-14 4:08 ` 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=20190313185259.GA4579@wolff.to \
--to=bruno@wolff.to \
--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 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.