Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp8682310ybi; Tue, 23 Jul 2019 13:03:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqyOhGOH6bhxY33dLinld0eWLe3G13123XVFxcN2CB09devjxWGVIaMiswl93vru8T9E61hm X-Received: by 2002:a63:f807:: with SMTP id n7mr80431530pgh.119.1563912224796; Tue, 23 Jul 2019 13:03:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563912224; cv=none; d=google.com; s=arc-20160816; b=JVT8uAzWtZTkvf266nFxrQFepKaGdP17XJ24EfuD4BH4ZjAxVWKk32reWl7JnULlK3 FT+c4t62/pnjwyr9kJXLVpyJELrM1LdIVo4xDZ9vHVw2BWCRuDm9GVbYXPerlX+dmVWO tUGVGn7mEnQxOPoWBO4/8IXgjMg/NnkP+Czo5I06MFAeOuaq2Rx/69lOv3FPSM08ro3l CLeP6vRr/rPzNYgd3rfrjtzXOyghs4M03T0F/CiXsvS9yaiU9EvRmyLp2eaXqE7QG64R 95PhlUehLFoYqehctw75oVRopPIt4RTu2klLdxWZ7qlC9jo/XjVt5yPix6gtvPibSXKF BtDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:cc:references:to :subject; bh=Go61K72jK+jrucYd0+pUNb2CNk5WhI8A7DqYG7lmY3Y=; b=JFn7zJL6JLPG0YAIm11oaxzgTLEzTP7fnqFMfsMEXEKiCoTI+MT9QBADL+6VMZ0GVf 9uGkHzk2lBJlV03bLfIjpoxWmcXYro38wGleTJLMocEsnoO7wg0NxUstJ+jiLgfwrEff Pmm23/+0g43PpU0sQ6DR0Jkq5s3S2z/nSplF2zv+1ErbkHJhUXYOskAre8gA1DjpoexV YCuV8rAb/yeN3nFRPjp2y87bZXC0TZydum5aq4+/ZVw7V09YJBSBJaLZYMEtOyzZpK+k Fwhjw8lRjP0UM/b/GZnZWFP7o7w9Gg/yQqrvCP7B4ZUyM8grD8DMkVS1iPK3zi7geyul Ch6g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i189si16234985pge.253.2019.07.23.13.03.23; Tue, 23 Jul 2019 13:03:44 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731635AbfGWKGh (ORCPT + 99 others); Tue, 23 Jul 2019 06:06:37 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:2738 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1729188AbfGWKGg (ORCPT ); Tue, 23 Jul 2019 06:06:36 -0400 Received: from DGGEMS410-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 7895113D89DE9AEC72C9; Tue, 23 Jul 2019 18:06:33 +0800 (CST) Received: from [127.0.0.1] (10.133.213.239) by DGGEMS410-HUB.china.huawei.com (10.3.19.210) with Microsoft SMTP Server id 14.3.439.0; Tue, 23 Jul 2019 18:06:24 +0800 Subject: Re: [PATCH] RDMA/hns: Fix build error for hip08 To: Leon Romanovsky References: <20190723024908.11876-1-yuehaibing@huawei.com> <20190723074339.GJ5125@mtr-leonro.mtl.com> CC: , , , , , From: Yuehaibing Message-ID: Date: Tue, 23 Jul 2019 18:06:22 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20190723074339.GJ5125@mtr-leonro.mtl.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.133.213.239] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/7/23 15:43, Leon Romanovsky wrote: > On Tue, Jul 23, 2019 at 10:49:08AM +0800, YueHaibing wrote: >> If INFINIBAND_HNS_HIP08 is selected and HNS3 is m, >> but INFINIBAND_HNS is y, building fails: >> >> drivers/infiniband/hw/hns/hns_roce_hw_v2.o: In function `hns_roce_hw_v2_exit': >> hns_roce_hw_v2.c:(.exit.text+0xd): undefined reference to `hnae3_unregister_client' >> drivers/infiniband/hw/hns/hns_roce_hw_v2.o: In function `hns_roce_hw_v2_init': >> hns_roce_hw_v2.c:(.init.text+0xd): undefined reference to `hnae3_register_client' > > It means that you have a problem with header files of your hns3. hnae3_unregister_client is a EXPORT_SYMBOL. If INFINIBAND_HNS is y, hns-roce-hw-v2 will be built-in, but as HNS3 is set to m, linking will failed. I can't see how to fix this in header files of hns3, or am I missing something? > >> >> Reported-by: Hulk Robot >> Fixes: dd74282df573 ("RDMA/hns: Initialize the PCI device for hip08 RoCE") >> Signed-off-by: YueHaibing >> --- >> drivers/infiniband/hw/hns/Kconfig | 3 ++- >> 1 file changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/infiniband/hw/hns/Kconfig b/drivers/infiniband/hw/hns/Kconfig >> index b59da5d..4371c80 100644 >> --- a/drivers/infiniband/hw/hns/Kconfig >> +++ b/drivers/infiniband/hw/hns/Kconfig >> @@ -23,7 +23,8 @@ config INFINIBAND_HNS_HIP06 >> >> config INFINIBAND_HNS_HIP08 >> bool "Hisilicon Hip08 Family RoCE support" >> - depends on INFINIBAND_HNS && PCI && HNS3 >> + depends on INFINIBAND_HNS && (INFINIBAND_HNS = HNS3) > > This is wrong. > >> + depends on PCI >> ---help--- >> RoCE driver support for Hisilicon RoCE engine in Hisilicon Hip08 SoC. >> The RoCE engine is a PCI device. >> -- >> 2.7.4 >> >> > > . >