Received: by 2002:a05:6a10:17d3:0:0:0:0 with SMTP id hz19csp2753302pxb; Mon, 19 Apr 2021 13:03:13 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwgrYpmRmQaZsFqU0BSMvsQxqBpo2rzDtYfIaTBR+PbXsml1ERi1kK6gl4etHjkmjBTThOo X-Received: by 2002:a17:90b:e82:: with SMTP id fv2mr871663pjb.139.1618862593154; Mon, 19 Apr 2021 13:03:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1618862593; cv=none; d=google.com; s=arc-20160816; b=ff69n82PEd7lsKYmZi41G7Xf9iQrltsu32ODd31neVeXrzKuxTUYe/otacOqtixh95 1nXFqufMiXuDly9ZCUh2uuetLxac48r2Xyd0uAM0wqwSNTDGr/1ZLQWV25aGJYgJJKzt KvP4Uls8f6B++fQNlbKiBU1DKgwS5xgyNM4kEcGhdIADpNWX/t17JC2FDtI0Ivaz3sP1 decnkxzvDoAy3ySg6MZh/jiAKaqLGgcy5eRGrVag7RilHlAsHoBqAgNsz4PPl4vY5muI 1afhyLCWOVC/ac+4I82l0/rScrbFFOijEePcDhnSKvyhSObcxoEfmNhquQHHseNwc252 jgEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:subject:from :references:cc:to; bh=2Kna10lswPMw68Lwo7GAPup/kUwp4IlGaRd2MwF1Dlk=; b=WvjrMuSVES9pcZpsBtgGzP1HnKkRQ8sSsiijwLo5yO3c+0CGpcaQMV+nHOYRutUvOW +aJsGPePQNKXJtpblr1G+x7sMkPziMtHTvzew0aAxncAX82UHSqtXlTXrcPB/gz008Wc LPkgLpW9+3uCsOq1Z81MVDU/6U3QE+Xh2nS0UVxylG0gRvM33ESkg6OUV69cZ+xmSfcd itDrOe54AUtXkJqo0avFW+3jiZQTQ7/uRuDC5EhOFF9pWcYXWkqKYkkSn+P4ncOZIBl3 1pg6C6W1mTPpQ0MNrp70xZld2odSb3xvipe3GQfidTnX3XfbDi0fmqAqOMB1tO808aIU Fmgw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id t134si11135843pgc.41.2021.04.19.13.02.57; Mon, 19 Apr 2021 13:03:13 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238649AbhDSQ1V (ORCPT + 99 others); Mon, 19 Apr 2021 12:27:21 -0400 Received: from mx2.suse.de ([195.135.220.15]:47156 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230063AbhDSQ1U (ORCPT ); Mon, 19 Apr 2021 12:27:20 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id C4DD3AF11; Mon, 19 Apr 2021 16:26:49 +0000 (UTC) To: Randy Dunlap , Stephen Rothwell , Linux Next Mailing List Cc: Linux Kernel Mailing List , "linux-block@vger.kernel.org" , linux-bcache@vger.kernel.org, Kent Overstreet References: <20210419202309.0575ad77@canb.auug.org.au> <66d41349-60ba-f27f-5c56-3520a40dd83f@infradead.org> From: Coly Li Subject: Re: linux-next: Tree for Apr 19 (bcache) Message-ID: Date: Tue, 20 Apr 2021 00:26:45 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.1 MIME-Version: 1.0 In-Reply-To: <66d41349-60ba-f27f-5c56-3520a40dd83f@infradead.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/19/21 11:40 PM, Randy Dunlap wrote: > On 4/19/21 3:23 AM, Stephen Rothwell wrote: >> Hi all, >> >> Changes since 20210416: >> > > on x86_64: > > when > # CONFIG_BLK_DEV is not set > > > WARNING: unmet direct dependencies detected for LIBNVDIMM > Depends on [n]: PHYS_ADDR_T_64BIT [=y] && HAS_IOMEM [=y] && BLK_DEV [=n] > Selected by [y]: > - BCACHE_NVM_PAGES [=y] && MD [=y] && BCACHE [=y] && PHYS_ADDR_T_64BIT [=y] > > > Full randconfig file is attached. > I need hint from kbuild expert. My original idea to use "select LIBNVDIMM" is to avoid the BCACHE_NVM_PAGES option to disappear if LIBNVDIMM is not enabled. Otherwise if nvdimm driver is not configure, users won't know there is a BCACHE_NVM_PAGES option unless they read bcache Kconfig file. But I see nvdimm's Kconfig, it uses "depends on BLK_DEV", I understand it is acceptable that LIBNVDIMM option to disappear from "make menuconfig" if BLK_DEV is not enabled. For such condition, which one is the proper way to set the dependence ? - Change "select LIBNVDIMM" and "select DAX" to "depends on LIBNVDIMM" and "depends on DAX" in bcache Kconfig - Or change "depends on BLK_DEV" to "select BLK_DEV" in nvdimm Kconfig. I want to ask for a proper way to handle such dependence, and I will follow the guide for now and in future. Thanks in advance for the advice. Coly Li