From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: David Miller <davem@davemloft.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
Netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: WireGuard to port to existing Crypto API
Date: Wed, 25 Sep 2019 12:14:40 +0200 [thread overview]
Message-ID: <CAHmME9qK2RWPLWWZGcmtVEHz+vUaVRBNtjv3GutkzWccdogF0w@mail.gmail.com> (raw)
In-Reply-To: <20190925.113928.2046484827308019751.davem@davemloft.net>
Hi Dave,
On Wed, Sep 25, 2019 at 12:03 PM David Miller <davem@davemloft.net> wrote:
> I didn't say "must" anything, I suggested this as a more smoothe
> and efficient way forward.
s/must/should/g? However it's characterized, I think your jugements
and opinions are generally sound, and I intend to put them into
action.
> I'm also a bit disappointed that you felt the need to so quickly
> make such an explosive posting to the mailing list when we've
Explosive? That's certainly not the intent here. The project is
changing direction in a big way. Collaborating with others on the
crypto API will be an important part of that. Announcing the change in
direction, those intentions, a rationale on why it will be okay, and
inviting collaboration is a responsible thing to do at the earliest
opportunity. Better to announce intent early rather than surprise
people or deter potential collaborators by keeping plans secret.
Jason
next prev parent reply other threads:[~2019-09-25 10:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 8:29 WireGuard to port to existing Crypto API Jason A. Donenfeld
2019-09-25 8:46 ` Toke Høiland-Jørgensen
2019-09-25 9:17 ` Bruno Wolff III
2019-09-25 9:40 ` David Miller
2019-09-25 9:39 ` David Miller
2019-09-25 10:14 ` Jason A. Donenfeld [this message]
2019-09-29 18:31 ` David Sterba
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=CAHmME9qK2RWPLWWZGcmtVEHz+vUaVRBNtjv3GutkzWccdogF0w@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).