From: pavrampu <pavrampu@linux.ibm.com>
To: tyreld@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, venkat88@linux.ibm.com
Subject: scsi: ibmvfc: Add Kconfig dependency on NVME_FC to prevent link failure
Date: Wed, 02 Sep 2026 13:55:02 +0530 [thread overview]
Message-ID: <327877a29337aa526cc50ac88fbddb86@linux.ibm.com> (raw)
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'
If you happen to fix this, please add below tag.
Reported-by: Pavithra <pavrampu@linux.ibm.com>
Thanks,
Pavithra
next reply other threads:[~2026-09-02 8:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 8:25 pavrampu [this message]
2026-09-02 8:40 ` scsi: ibmvfc: Add Kconfig dependency on NVME_FC to prevent link failure Venkat Rao Bagalkote
2026-09-03 1:27 ` Tyrel Datwyler
2026-09-03 7:46 ` Venkat Rao Bagalkote
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=327877a29337aa526cc50ac88fbddb86@linux.ibm.com \
--to=pavrampu@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=tyreld@linux.ibm.com \
--cc=venkat88@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