Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1453065pxb; Wed, 12 Jan 2022 15:21:12 -0800 (PST) X-Google-Smtp-Source: ABdhPJxNnyBQ+w9Z+u4njwouBeIV7vsXk5vIzVMecW0vww6FDZWK9tczue7tCJ5D+zDRbLHUNzbz X-Received: by 2002:a17:902:6a8b:b0:149:82bb:560a with SMTP id n11-20020a1709026a8b00b0014982bb560amr2039419plk.158.1642029672607; Wed, 12 Jan 2022 15:21:12 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642029672; cv=none; d=google.com; s=arc-20160816; b=IJKrFf/mqES+9Pg44fiEuaEo7MkfKXYJ+IXb1FwwjzPRp0CuOadBtbHuKabm/AipUc MJ453UpkEYV0xUknzTHPFi1lCyRT6ri+P1SVMIAbFMLDE7Gyo2Ur4IqyrYCbgJXgnHeJ dsP+9DwMbxdQO1bklaqY1TypINrEmXC8f13II0Ixko1SzUe+2pCMbLgAqO/G6hqN+gr6 W3PnzC/6ZjoD4YXlJZ160LqPYAlvaeZFI017OZBWfmbzlOtpXYoM0/0nFpTH3xWS5VvN ew8bYYznKcJcLF9bdt26ZFzwW/QHTPQFChkkA4sfDmSj9Mh8AeeFOHltsDYVgicEWzwe 2q+A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=OvxDuX4+u+Vf1kkrJDUSgv4TPdU3VRNAUcdKXCwTT5c=; b=Sd97EZlgo0HYxCGQnsUSbCJIG3TT9u8h0Lu8UX3M82QZb0lxnhE76TbeX2AyM0DM9Y HZtsHuznoGzB1fMnwawX13QrcITquyw3Vcqy694jv3V6my8JobgCev2in8zYaaBgDwf5 ydGa65w2ZJ4fF9mllvzI2yReduyRR95eLz1cx7tqpQPpmYAm3n6/mlGHEfIaL7RmQ3Hp DHEBHsPT79WFuXBiIRrG8N6rebx/xjN9zMMqKZeMLOeZ+XP9ivnWz5kPY0EzDOzr2lOq IiZKCLezWgfakCFXUDzfwUb6ry1c9qm1oZJbWfL7WqUWjjGfYWnQWCVoM9bXyr6YrLN+ Ygsg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=DnJhczWU; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t11si1402972pgl.673.2022.01.12.15.21.00; Wed, 12 Jan 2022 15:21:12 -0800 (PST) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=20210105 header.b=DnJhczWU; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1354340AbiALOxp (ORCPT + 99 others); Wed, 12 Jan 2022 09:53:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53048 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242867AbiALOxo (ORCPT ); Wed, 12 Jan 2022 09:53:44 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 54F74C06173F; Wed, 12 Jan 2022 06:53:44 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id E9B45618D6; Wed, 12 Jan 2022 14:53:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id F21DFC36AE5; Wed, 12 Jan 2022 14:53:42 +0000 (UTC) Authentication-Results: smtp.kernel.org; dkim=pass (1024-bit key) header.d=zx2c4.com header.i=@zx2c4.com header.b="DnJhczWU" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zx2c4.com; s=20210105; t=1641999220; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OvxDuX4+u+Vf1kkrJDUSgv4TPdU3VRNAUcdKXCwTT5c=; b=DnJhczWUUvD9OTeps1orXgX12AsBGp8v848iAIhv/ZzalybRxXv6B+W0wFW1EvIgePDNd5 5BFnz3pj0i7cmnVA5+7UVWIR4xX5E+ZaRghwy95P6vsOX/GiJjrV8wcSWThUm5LkEcga/3 KA8n/vlCNHW0k1FN13d0g11tFVP9uA0= Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 7ed3ec98 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 12 Jan 2022 14:53:39 +0000 (UTC) Received: by mail-yb1-f170.google.com with SMTP id p187so7236263ybc.0; Wed, 12 Jan 2022 06:53:39 -0800 (PST) X-Gm-Message-State: AOAM530cwaiY/Rbwpt1gU6ucBwwoq3ocSJthWHQg+t5VUXMcHKC3NbcJ fn5DfLy0z28eXBLPJAigsyOauF839wpQ0U+JXmE= X-Received: by 2002:a25:854f:: with SMTP id f15mr3731ybn.121.1641999218396; Wed, 12 Jan 2022 06:53:38 -0800 (PST) MIME-Version: 1.0 References: <20220112140137.728162-1-jforbes@fedoraproject.org> In-Reply-To: From: "Jason A. Donenfeld" Date: Wed, 12 Jan 2022 15:53:27 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2] lib/crypto: add prompts back to crypto libraries To: Ard Biesheuvel Cc: "Justin M. Forbes" , Herbert Xu , "David S. Miller" , Greg Kroah-Hartman , Linux Crypto Mailing List , LKML , Justin Forbes , Linux Kbuild mailing list Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org On Wed, Jan 12, 2022 at 3:50 PM Ard Biesheuvel wrote: > > Sure, but none of this is relevant for the short term fix that we need > to get in asap. There are lots of future changes we can philosophize > about, but those discussions should take place on the linux-crypto > list after the merge window closes. I think of adding things to the root menu as a regression. I'd like to avoid an additional regression in fixing this. > > > and given that this > > > patch is presumably going to be sent as an early fix on top of your > > > rng branch, it is better not to touch anything under crypto/ unless > > > you are 100% certain it is not going to conflict with Herbert's tree. > > > > Oh, I was thinking Herbert would take this since he hasn't sent a pull > > yet? Otherwise, sure, I can do it. > > > > How could he? This patch does not apply to his cryptodev tree, which > won't receive backmerges from mainline until the next cycle. Oh, okay then. I'll take it. In which case, I really don't want to be the one responsible for mucking up the root menu with something nobody cares about (crypto library submenu). I'll fix up the menu location thing locally then and send a v3 here. Jason