From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 18FDEC432C2 for ; Wed, 25 Sep 2019 09:39:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id E9BB52082F for ; Wed, 25 Sep 2019 09:39:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726504AbfIYJjg (ORCPT ); Wed, 25 Sep 2019 05:39:36 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:33496 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725842AbfIYJjf (ORCPT ); Wed, 25 Sep 2019 05:39:35 -0400 Received: from localhost (unknown [65.39.69.237]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 76B5A15492860; Wed, 25 Sep 2019 02:39:34 -0700 (PDT) Date: Wed, 25 Sep 2019 11:39:28 +0200 (CEST) Message-Id: <20190925.113928.2046484827308019751.davem@davemloft.net> To: Jason@zx2c4.com Cc: wireguard@lists.zx2c4.com, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: WireGuard to port to existing Crypto API From: David Miller In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Wed, 25 Sep 2019 02:39:35 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Jason A. Donenfeld" Date: Wed, 25 Sep 2019 10:29:45 +0200 > His viewpoint has recently solidified: in order to go upstream, > WireGuard must port to the existing crypto API, and handle the Zinc > project separately. I didn't say "must" anything, I suggested this as a more smoothe and efficient way forward. 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 just spoken about this amongst ourselves only 20 minutes ago. Please proceed in a more smoothe and considerate manner for all parties involved. Thank you.