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=-2.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 11447C433E0 for ; Tue, 23 Feb 2021 21:55:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C54BA64EC3 for ; Tue, 23 Feb 2021 21:55:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232046AbhBWVzL (ORCPT ); Tue, 23 Feb 2021 16:55:11 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40390 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230268AbhBWVzF (ORCPT ); Tue, 23 Feb 2021 16:55:05 -0500 Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ADEADC061574; Tue, 23 Feb 2021 13:54:40 -0800 (PST) Received: by mail-qt1-x831.google.com with SMTP id c1so15295qtc.1; Tue, 23 Feb 2021 13:54:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=/2YQl5j1lSOrAsVX4Tf33JuArsqON9FAJrHoqBhvUAY=; b=SjL74SvJbXYEkIKRmaESz2/LOhR/fjSCIQlBo0t9SDZgvgnPExxSf75AcToNpc7ly2 RW/2vpEL6qwoZDXLpGPsthZccUfSK4m9mNnP/USqPt71YkkCbkYXM9Wlqu200pLoJUSt KC+9tL9vYWTr3imlHgR6AT53O2+8UNXwYBZO/jSXoCDxqqkYFwgau5I3lF6/RrTkhLZz lXRyhuWK0fjeMWBMBiu6nqE7y6tRk6BwTf5RBra+OXBYx4SPKkfXve7Rr141B6+No5nq r+jz5grHZfCizJqtkkTuMrSChWfPLw6K/+ZKNGWuHOmzYAgytgM0fgXRvf4PR2HTp59g k2Uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:date:message-id :in-reply-to:references:mime-version:content-transfer-encoding; bh=/2YQl5j1lSOrAsVX4Tf33JuArsqON9FAJrHoqBhvUAY=; b=Xr3LiPHFnGE8z0Bnkrf4AvZ7bJ+uHL/VIV96Gcmtig4a1S9EVKAXJwjeU9+rdAa+J7 ef2zq5HtBezT9aehCU3pMH9M312MxnZW+qiASRbzVJOCm+rOwC5fivRQoYL9e0bP/Zk+ XkSPCKVgfl2398Ht63+HovmpvI76PkVYvaeGpVNhF3kYgcJkCB3l+vYVL/3Q8jaZAECG 71iTjJCAwDKOQqlVWTl3HJ5K3MEzPch6bBUBlnYWYF19Hk7fJkUQ12z289BAPHRDiTgI RKuNLd4x+pSrPbHXcchxpADjd22m3e6HWEr7jd13Wfl0DbEm7Jas+rmlsUf5Fi+59V8B AH5w== X-Gm-Message-State: AOAM533lefhSZ86uxK34wGJBhpKX1Frb1ihz773SxpzANJSmDvUlmqXt JL4UHIb6soejZZ8Ai+sI1yM= X-Google-Smtp-Source: ABdhPJx1Ohe2fn4HMWjqXJHYzXGca6gc4EdzEanQQP7Ro4JcSnT4WwVaHLzZ9Ckw7PpL1SKFGVPtfg== X-Received: by 2002:ac8:5992:: with SMTP id e18mr26827902qte.177.1614117279726; Tue, 23 Feb 2021 13:54:39 -0800 (PST) Received: from ubuntu-mate-laptop.localnet (108-188-130-030.biz.spectrum.com. [108.188.130.30]) by smtp.gmail.com with ESMTPSA id 80sm95389qkm.45.2021.02.23.13.54.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Feb 2021 13:54:39 -0800 (PST) Sender: Julian Braha From: Julian Braha To: Arnd Bergmann Cc: Randy Dunlap , Jason Gunthorpe , Leon Romanovsky , Arnd Bergmann , Zhu Yanjun , Doug Ledford , RDMA mailing list , LKML Subject: Re: [PATCH] drivers: infiniband: sw: rxe: fix kconfig dependency on CRYPTO Date: Tue, 23 Feb 2021 16:54:37 -0500 Message-ID: <10464303.FBcTZR2von@ubuntu-mate-laptop> In-Reply-To: References: <21525878.NYvzQUHefP@ubuntu-mate-laptop> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, February 23, 2021 4:26:44 PM EST Arnd Bergmann wrote: > On Tue, Feb 23, 2021 at 9:46 PM Julian Braha wrote: > > > > I have other similar patches that I intend to submit. What should I do, > > going forward? Should I use "depends on CRYPTO" for cases like these? > > Should I resubmit this patch with that change? > > No, we should not mix the two methods, that just leads to circular dependencies. > > How many more patches do you have that need to get merged? > > If it's only a few, I'd suggest merging them first before we consider a > broader change. If the problem is very common, we may want to > think about alternative approaches first, and then change everything > at once. > > Arnd > Sorry, I don't have a specific number, but it's certainly under a dozen patches.