From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Bruno Wolff III <bruno@wolff.to>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Kernel commit d35a00b8e33dab7385f724e713ae71c8be0a49f4 breaks wireguard
Date: Mon, 27 Feb 2017 16:51:58 -0800 [thread overview]
Message-ID: <CAHmME9reptbL33VU4eapc7Q7jrhU2J+eA2T71kdw7y1apWFSQQ@mail.gmail.com> (raw)
In-Reply-To: <20170228002424.GA18437@wolff.to>
Hey Bruno,
Excellent, thanks for checking.
By the way, after rc1 is released, wireguard.io/build-status/ will
automatically start compiling every version on it, so we'll get good
code coverage that way. You're just a bit ahead of the curve :).
Jason
prev parent reply other threads:[~2017-02-28 0:50 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
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 [this message]
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=CAHmME9reptbL33VU4eapc7Q7jrhU2J+eA2T71kdw7y1apWFSQQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=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 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).