From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel commit d35a00b8e33dab7385f724e713ae71c8be0a49f4 breaks wireguard
Date: Mon, 27 Feb 2017 16:14:44 -0600 [thread overview]
Message-ID: <20170227221444.GA11938@wolff.to> (raw)
In-Reply-To: <CAHmME9ryT7LWjs+-D4VJpd3DBSQeBa0hUtDUcJ3gBt46xUobiA@mail.gmail.com>
On Mon, Feb 27, 2017 at 14:10:18 -0800,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Thanks! I wasn't compiling with the options to hit this, so I didn't
>see it before. Should be fixed now.
Thank you.
It now builds cleanly and it at least appears to be working correctly in
simple testing.
next prev parent reply other threads:[~2017-02-27 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 18:04 Bruno Wolff III
2017-02-27 20:10 ` Jason A. Donenfeld
2017-02-27 20:22 ` Bruno Wolff III
2017-02-27 20:37 ` Bruno Wolff III
2017-02-27 22:10 ` Jason A. Donenfeld
2017-02-27 22:14 ` Bruno Wolff III [this message]
2017-02-27 22:37 ` Bruno Wolff III
2017-02-27 23:03 ` Jason A. Donenfeld
2017-02-28 0:24 ` Bruno Wolff III
2017-02-28 0:51 ` Jason A. Donenfeld
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=20170227221444.GA11938@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.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).