Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp823407imw; Mon, 4 Jul 2022 21:35:13 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vKENyKIkjtJq7YrE+PodUqq9cQLzxVBm0uRn/9XYdB7lliGkjyjR5po5X688Ol0hqGmVhW X-Received: by 2002:a17:90b:4ac9:b0:1ec:9bd1:92ff with SMTP id mh9-20020a17090b4ac900b001ec9bd192ffmr38401823pjb.178.1656995712943; Mon, 04 Jul 2022 21:35:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656995712; cv=none; d=google.com; s=arc-20160816; b=jkHhjU6uaSZzmuzEHDvcVCo2Sq0Ox4+tKZsDeRSJjYll8kxwE2yMk7JO6bbNjVb+bg dmElpiX3UJXTRYobtqGbwrsWf6kWmkuxvvv62wVS1vM8k6ojdLhK07qPUQJMaUjmwvcV hoWzu4AyEGoKry8crKDysa/Gj7AlKsWwiITClb4plHvJyfG9AufhRhe7XYZPi2Y9+hEN 9ajHO3yXe7HoUpQ/5bTibh5Pr3PHr2MRQK3CFZ70DFM0KqB1+cXBLwYGy1GKG2dRK3Go 9p26cuJrI13/L1I7f2igdKwiYd/wTbNsazATJ+ADyEVFtPl4fAHRmcGD1lrzGcpo5lLB jUrQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=kRMVwQLChKyddODrguodCavxb+l4lJcNvKrMnoCP3bk=; b=S3PURMPfaU2LonTrG3G+VuLTJ+TLX7no+B7aiFeShPUAEP5VErdyIXGRYjZ/RvPu/a icqQOG38ujFYR/EVBoLCBt0HBj0HqKngYCKHuizjAOAFSNW5TkB8a8sLu4nftg8LyeRK d/9RM22ZyKMB434AB275dyiSYhmdJ+upK54yguIc72BexUn5q8nA62ensobe9RVlgaRG PQG6LtUsqkqByUsJM5Z1XkKmPWA7XbwefZEsjmhMOGL3UPcSFM2wcDh0pRfkzFkF4ngT TF9qpDTp9zqPXdQa59aceR2MbvKR99ZZfnScDXNrRg/DGbI/e1Ns+xuKp1ibFPgaPY79 Jf8w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id nk2-20020a17090b194200b001ef920453d0si2844113pjb.119.2022.07.04.21.34.47; Mon, 04 Jul 2022 21:35:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231189AbiGEE32 (ORCPT + 99 others); Tue, 5 Jul 2022 00:29:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50002 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229883AbiGEE32 (ORCPT ); Tue, 5 Jul 2022 00:29:28 -0400 Received: from fornost.hmeau.com (helcar.hmeau.com [216.24.177.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D1382117B; Mon, 4 Jul 2022 21:29:26 -0700 (PDT) Received: from gwarestrin.arnor.me.apana.org.au ([192.168.103.7]) by fornost.hmeau.com with smtp (Exim 4.94.2 #2 (Debian)) id 1o8aBK-00EVKV-7S; Tue, 05 Jul 2022 14:29:03 +1000 Received: by gwarestrin.arnor.me.apana.org.au (sSMTP sendmail emulation); Tue, 05 Jul 2022 12:29:02 +0800 Date: Tue, 5 Jul 2022 12:29:02 +0800 From: Herbert Xu To: Jakub Kicinski Cc: Taehee Yoo , linux-crypto@vger.kernel.org, davem@davemloft.net, borisp@nvidia.com, john.fastabend@gmail.com, daniel@iogearbox.net, edumazet@google.com, pabeni@redhat.com, netdev@vger.kernel.org Subject: Re: [PATCH v2 3/3] net: tls: Add ARIA-GCM algorithm Message-ID: References: <20220704094250.4265-1-ap420073@gmail.com> <20220704094250.4265-4-ap420073@gmail.com> <20220704201009.34fb8aa8@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220704201009.34fb8aa8@kernel.org> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Mon, Jul 04, 2022 at 08:10:09PM -0700, Jakub Kicinski wrote: > > Is it okay if you send the crypto patches now and the TLS support after > the merge window? They go via different trees and we can't take the TLS > patches until we get the crypto stuff in net-next. We could work > something out and create a stable branch that both Herbert and us would > pull but we're getting close to the merge window, perhaps we can just > wait? I need to know that you guys will take the network part of the patch in order to accept the crypto part. We don't add algorithms with no in-kernel users. As long as you are happy to take the TLS part later, we can add the crypto parts right now. Thanks, -- Email: Herbert Xu Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt