Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp2796015pxp; Mon, 14 Mar 2022 05:15:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz3eUTBMJpm/tx6gcDCz99Gl8bAoADHl7LJIldKA3de2eVmKrRRR9PRlIftaT5HablNdKTi X-Received: by 2002:a17:906:4fc7:b0:6da:92b2:f572 with SMTP id i7-20020a1709064fc700b006da92b2f572mr18135589ejw.184.1647260142975; Mon, 14 Mar 2022 05:15:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1647260142; cv=none; d=google.com; s=arc-20160816; b=jWb7ykPUaPQO3uu1af1hkUAgAMHB5T9dGJ1etiD302xr1iaZB1cEUQcpzhpqSJJ9Ck SSI728K+tpop26iBEgLQ5sVS/cQoYIxYawfVJdYTvl6tfhhyRp39JIWOmxYb0/AGsiAM HjMH5qJ2Qkuv+afi1qPEd0/OjHHPztblD/G5tGXMCmDVLlEMBpDM7vJzs8O9ZUJtElPk hxBYraEfBnpZprysk0usf1FylcJnljKuEu2H7bLQ3+/6YBA1Py/yOaIjSNhpGDbz0IQA meSxutcVjMP1Ul6q+nhdVGfqpA9Fs2NsrRQOF8dMbRR/Mllbhw2NirpSFtEjLQPttRvL COBg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=H+ZrdKEXKEGrT5jOhUGJAlN2MccDjHKg9oyR2nKfTgc=; b=wO5XmqjaRyEt9F3c7Eock4ciLVlDE77pfoi/WZC2oYEhzixLAQQVPZ7lGYDb1mnV/m ezw2oDK0o0farvbvNdY9LJXcd1Ra/aU6AIwYga6011ea3jxI9GhTbt0KauuCEjJWMYhq jM1ZE2Cmlk2epTTSmX7pj3wj8qJH8ZHVo3XRwnPQmuNZistVeKu5PiEADQhqR7FcFyUx W4LBeK+WjjCNz/y1ig56VnJcYKPEAzUEgkqWuaPAIpMPbH/ptIzi7pGLHN7W572p7rm3 Q7prixY9MlDMokPvqcj5bHGVvBxeTb/rLAh0MGX5p2rEB/iKsFL64EmZaKuTp2r1baju UcwA== 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 x7-20020a170906148700b006d159679417si9739840ejc.958.2022.03.14.05.15.17; Mon, 14 Mar 2022 05:15:42 -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 S234218AbiCNHHN (ORCPT + 99 others); Mon, 14 Mar 2022 03:07:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56496 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236528AbiCNHHG (ORCPT ); Mon, 14 Mar 2022 03:07:06 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B5BAB40905 for ; Mon, 14 Mar 2022 00:05:57 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 3FB7F68B05; Mon, 14 Mar 2022 08:05:53 +0100 (CET) Date: Mon, 14 Mar 2022 08:05:52 +0100 From: Christoph Hellwig To: Hannes Reinecke Cc: Sagi Grimberg , Christoph Hellwig , Herbert Xu , Niolai Stange , Keith Busch , linux-nvme@lists.infradead.org, linux-crypto@vger.kernel.org Subject: Re: [PATCHv8 00/12] nvme: In-band authentication support Message-ID: <20220314070552.GA3806@lst.de> References: <9853d36a-036c-7f2b-5fb4-b3fb4bae473f@suse.de> <4328e4f0-9674-9362-4ed5-89ec7edba4a2@grimberg.me> <56f1ce1c-2272-bed2-fd6b-642854b612bb@suse.de> <483836f5-f850-6eac-8c38-3f03db3189ab@grimberg.me> <0c4613ff-ba30-c812-a6e9-1954d77b1d1b@suse.de> <1d1522c6-7f6b-7023-9e66-a05ac5a5a0be@grimberg.me> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,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, Mar 14, 2022 at 07:54:28AM +0100, Hannes Reinecke wrote: > Pondering what the next steps should be. Herbert Xu has merged Nicolais > patchset, so I _could_ submit the patches, but then I would need to base it > on Herberts cryptodev-2.6 branch. > And without these patches my patchset won't compile. > So no sure how to proceed; sending the patches relative to Herberts tree? > Waiting for the patches to appear upstream? Not sure what'll be best... We're at 5.17-rc8, so hopefully they will in mainline for 5.18-rc1 in a few weeks. Let's wait until then to avoid complex tree dependencies.