From: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
To: Tyrel Datwyler <tyreld@linux.ibm.com>, pavrampu <pavrampu@linux.ibm.com>
Cc: linux-scsi@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
brking@linux.ibm.com, linux-kernel@vger.kernel.org,
davemarq@linux.ibm.com
Subject: Re: scsi: ibmvfc: Add Kconfig dependency on NVME_FC to prevent link failure
Date: Thu, 3 Sep 2026 13:16:01 +0530 [thread overview]
Message-ID: <b9f8c317-f919-47f2-8988-e57e22176a82@linux.ibm.com> (raw)
In-Reply-To: <9873559a-59df-4f4c-b653-6930636096a6@linux.ibm.com>
On 03/09/26 6:57 am, Tyrel Datwyler wrote:
> On 9/2/26 1:40 AM, Venkat Rao Bagalkote wrote:
>> On 02/09/26 1:55 pm, pavrampu wrote:
>>> Hi,
>>>
>>> I am seeing below build failure with latest linux-next repo.
>>>
>>> Description:
>>>
>>> Building the kernel with CONFIG_SCSI_IBMVFC=y and CONFIG_NVME_FC=m results in
>>> a link failure when building vmlinux:
>>>
>>> Build failure logs:
>>>
>>> ld: drivers/scsi/ibmvscsi/ibmvfc-nvme.o: in function
>>> `ibmvfc_nvme_register_remoteport':
>>> ibmvfc-nvme.c:488: undefined reference to `nvme_fc_register_remoteport'
>>> ld: drivers/scsi/ibmvscsi/ibmvfc-nvme.o: in function
>>> `ibmvfc_nvme_unregister_remoteport':
>>> ibmvfc-nvme.c:515: undefined reference to `nvme_fc_unregister_remoteport'
>>> ld: drivers/scsi/ibmvscsi/ibmvfc-nvme.o: in function `ibmvfc_nvme_register':
>>> ibmvfc-nvme.c:536: undefined reference to `nvme_fc_register_localport'
>>> ld: drivers/scsi/ibmvscsi/ibmvfc-nvme.o: in function `ibmvfc_nvme_unregister':
>>> ibmvfc-nvme.c:565: undefined reference to `nvme_fc_unregister_localport'
>>> ld: drivers/scsi/ibmvscsi/ibmvfc-nvme.o: in function `ibmvfc_nvme_unregister':
>>> ibmvfc-nvme.c:565: undefined reference to `nvme_fc_unregister_localport'
>>> ld: drivers/scsi/ibmvscsi/ibmvfc-core.c:6798: undefined reference to
>>> `nvme_fc_rescan_remoteport'
>>
>> Below simple check in Kconfig fixes the build failure.
>>
>> If this is acceptable, then I will send a formal patch.
> Yep, need to force ibmvfc to be a module when NVME_FC isn't builtin, or NVME_FC
> must be disabled.
Thank you for confirming.
Link to Patch:
https://lore.kernel.org/all/20260903074329.6705-1-venkat88@linux.ibm.com/
Regards,
Venkat.
>
> -Tyrel
>> # git diff
>> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
>> index 4a2af0f702e1..6612d5d445e2 100644
>> --- a/drivers/scsi/Kconfig
>> +++ b/drivers/scsi/Kconfig
>> @@ -753,6 +753,7 @@ config SCSI_IBMVFC
>> tristate "IBM Virtual FC support"
>> depends on PPC_PSERIES && SCSI
>> depends on SCSI_FC_ATTRS
>> + depends on NVME_FC || NVME_FC=n
>> help
>> This is the IBM POWER Virtual FC Client
>>
>>
>> Regards,
>>
>> Venkat.
>>
>>> If you happen to fix this, please add below tag.
>>>
>>> Reported-by: Pavithra <pavrampu@linux.ibm.com>
>>>
>>> Thanks,
>>> Pavithra
prev parent reply other threads:[~2026-09-03 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 8:25 pavrampu
2026-09-02 8:40 ` Venkat Rao Bagalkote
2026-09-03 1:27 ` Tyrel Datwyler
2026-09-03 7:46 ` Venkat Rao Bagalkote [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9f8c317-f919-47f2-8988-e57e22176a82@linux.ibm.com \
--to=venkat88@linux.ibm.com \
--cc=brking@linux.ibm.com \
--cc=davemarq@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=pavrampu@linux.ibm.com \
--cc=tyreld@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®