From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751676AbdB0Byz (ORCPT ); Sun, 26 Feb 2017 20:54:55 -0500 Received: from ozlabs.org ([103.22.144.67]:33169 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751645AbdB0Byx (ORCPT ); Sun, 26 Feb 2017 20:54:53 -0500 Date: Mon, 27 Feb 2017 12:54:45 +1100 From: Stephen Rothwell To: James Bottomley Cc: "Martin K. Petersen" , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, James Smart , Dick Kennedy , Hannes Reinecke Subject: Re: linux-next: build failure after merge of the scsi-mkp tree Message-ID: <20170227125445.77571c8b@canb.auug.org.au> In-Reply-To: <20170223080639.753ac411@canb.auug.org.au> References: <20170222134119.42f26068@canb.auug.org.au> <20170223080639.753ac411@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi James, On Thu, 23 Feb 2017 08:06:39 +1100 Stephen Rothwell wrote: > > On Wed, 22 Feb 2017 13:41:19 +1100 Stephen Rothwell wrote: > > > > After merging the scsi-mkp tree, today's linux-next build (powerpc > > ppc64_defconfig) failed like this: > > > > ERROR: ".nvme_fc_unregister_remoteport" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvme_fc_unregister_localport" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvmet_fc_rcv_ls_req" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvmet_fc_rcv_fcp_req" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvme_fc_register_localport" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvme_fc_register_remoteport" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvmet_fc_register_targetport" [drivers/scsi/lpfc/lpfc.ko] undefined! > > ERROR: ".nvmet_fc_unregister_targetport" [drivers/scsi/lpfc/lpfc.ko] undefined! > > > > Caused by commit > > > > 462896e1808c ("scsi: lpfc: NVME Initiator: bind to nvme_fc api") > > > > # CONFIG_NVME_FC is not set > > > > Presumably a missing dependency. > > > > I have used the scsi-mkp from next-20170221 for today. > > Unfortunately, you have just merged this build failure into the scsi > tree :-( > > James Smart has posted a fix: > > "[PATCH v2] lpfc: add missing Kconfig NVME dependencies" I am still getting this failure in the scsi tree even though a fix has been merged into the scsi-mkp tree a few days ago. -- Cheers, Stephen Rothwell