Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4720498imm; Tue, 11 Sep 2018 16:58:02 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZsR9lO5lqMRITw0dIQ36o1QnxV86KPNKV4EpdVCtVBdS47YA+UY7t9er3YNjcVHxTP5RLJ X-Received: by 2002:a63:91:: with SMTP id 139-v6mr30915131pga.389.1536710282486; Tue, 11 Sep 2018 16:58:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536710282; cv=none; d=google.com; s=arc-20160816; b=m/A7HRm3ivwD8V7cuO7qjZAUSeHJnCyoN9UsAF0gT8XrMx1URvjWQVmGurtrnq9DWO 4O6+6LizkOgMrVf4uXl4sCZWaAk2W6NvYMS6AgJ6svj2km9V7mb5O0IKprY50spKWk0n 3OjNpR+GHTnjyMhWtP9FZkbZ2UaSMCGW+h30s7WPZleRYJMAppq5JFhsdC6EA3pOM5vc ixCx4H8IbTO/MAjB+4BoFrGTO1iG71J8/yHhgzbg+gBMy4cOikC/c16XzOAwp7Ny3ZcT x5tZ/+mg5tLKANiYBtMSzy6ioCX4b2GFKZtW0FuQE0f2aQNQw1tGtYomJ8atjv3ixZNY vZIA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=Vc3bui6dJTI+NPnHD1K1kOcrLgpMIGlEu+eBXzExRGE=; b=h6bmTpQygD47AS1Xa9ZRJMNdZ/Lrdbb7rjK93YRQK9QkdRxtXYXAKvsuabdsV6BzBo zSVavKglBmdzfeLvo8r1SbyxeNa2YJ5aEWaGj4rKdLdcTcSfiTVVRosyX6FcAWxUT4zl Kel6EMTGCk69JQE/4Yjvk/2FE6jS22PPXYHkQG8hCMIXcYaM8zYQBFDkNIEanRMvioMu D6I34Bh8ShWK8ocQUqiGsA3XG+wawkuN0s5PYIMJObpDnpGeX08jilORNKcFJyDVAuD7 bh90ToZyKwcBvqYiUda/TKnrZRZWjdaL7TrpkBN+jDHTUm02fc2iq5rBkfmTG/Bl72TS +Vlw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s71-v6si20724952pgs.499.2018.09.11.16.57.47; Tue, 11 Sep 2018 16:58:02 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727984AbeILE7U (ORCPT + 99 others); Wed, 12 Sep 2018 00:59:20 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:54286 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725936AbeILE7U (ORCPT ); Wed, 12 Sep 2018 00:59:20 -0400 Received: from localhost (74-93-104-98-Washington.hfc.comcastbusiness.net [74.93.104.98]) (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 AE88C128F4EA1; Tue, 11 Sep 2018 16:57:39 -0700 (PDT) Date: Tue, 11 Sep 2018 16:57:39 -0700 (PDT) Message-Id: <20180911.165739.2032677219588723041.davem@davemloft.net> To: andrew@lunn.ch Cc: Jason@zx2c4.com, ebiggers@kernel.org, gregkh@linuxfoundation.org, ard.biesheuvel@linaro.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, luto@kernel.org, sneves@dei.uc.pt, jeanphilippe.aumasson@gmail.com, linux-crypto@vger.kernel.org Subject: Re: [PATCH net-next v3 02/17] zinc: introduce minimal cryptography library From: David Miller In-Reply-To: <20180911233015.GD11474@lunn.ch> References: <20180911214737.GA81235@gmail.com> <20180911233015.GD11474@lunn.ch> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) 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]); Tue, 11 Sep 2018 16:57:40 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Andrew Lunn Date: Wed, 12 Sep 2018 01:30:15 +0200 > Just as an FYI: > > 1) I don't think anybody in netdev has taken a serious look at the > network code yet. There is little point until the controversial part > of the code, Zinc, has been sorted out. > > 2) I personally would be surprised if DaveM took this code without > having an Acked-by from the crypto subsystem people. In the same way, > i doubt the crypto people would take an Ethernet driver without having > DaveM's Acked-by. Both of Andrew's statements are completely true. I'm not looking at any of the networking bits until the crypto stuff is fully sorted and fully supported and Ack'd by crypto folks.