From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] WireGuard: next generation secure network tunnel
Date: Fri, 1 Jul 2016 18:42:06 -0500 [thread overview]
Message-ID: <20160701234206.GA4367@wolff.to> (raw)
In-Reply-To: <b41c6b79-1c62-b3b2-4f8f-71a53e2babc4@zx2c4.com>
On Sat, Jul 02, 2016 at 01:03:17 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Hey Bruno,
>
>Sorry I didn't reply to this earlier; the message didn't make it to me
>somehow.
I only sent it to LKML, since we had communicated separately when you helped
me by making changes for the 4.7 kernel, I didn't think you needed to be
copied.
Having actual people using patches can help get them upstreamed, so I wanted
people to see that it was being used.
prev parent reply other threads:[~2016-07-01 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 14:49 [RFC] WireGuard: next generation secure network tunnel Jason A. Donenfeld
2016-06-30 0:34 ` Bruno Wolff III
2016-07-01 11:42 ` Richard Weinberger
2016-07-01 14:25 ` Jason A. Donenfeld
2016-07-01 14:47 ` Richard Weinberger
2016-07-01 23:03 ` Jason A. Donenfeld
2016-07-01 23:42 ` Bruno Wolff III [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=20160701234206.GA4367@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.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).