From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Mark Brown <broonie@kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in final build
Date: Mon, 13 Jul 2026 11:46:18 -0700 [thread overview]
Message-ID: <ae09fc06-ce41-424f-9643-5051f6256fdb@linux.ibm.com> (raw)
In-Reply-To: <alUWw0b334Y1AiRa@sirena.org.uk>
On 7/13/26 9:48 AM, Mark Brown wrote:
> Hi all,
>
> After merging the kthread tree, today's linux-next build
> (powerpc pseries_le_defconfig) failed like this:
>
> ERROR: modpost: "nvme_fc_rescan_remoteport" [drivers/scsi/ibmvscsi/ibmvfc.ko] undefined!
> ERROR: modpost: "nvme_fc_unregister_remoteport" [drivers/scsi/ibmvscsi/ibmvfc.ko] undefined!
> ERROR: modpost: "nvme_fc_unregister_localport" [drivers/scsi/ibmvscsi/ibmvfc.ko] undefined!
> ERROR: modpost: "nvme_fc_register_remoteport" [drivers/scsi/ibmvscsi/ibmvfc.ko] undefined!
> ERROR: modpost: "nvme_fc_register_localport" [drivers/scsi/ibmvscsi/ibmvfc.ko] undefined!
>
> Caused by commit
>
> ddbcf78e8d230 (scsi: ibmvfc: Process NVMe/FC rports in work thread)
>
> I have used the version from next-20260710 instead (equivalent to
> dropping the tree since everything seems to be new today).
This is from the NVMf ibmvfc patch series. I've asked Martin to drop it from
scsi-staging as I already had a respin in process to send out, plus I clearly
forgot to gate the NVMf functionality on NVMf support being configured.
-Tyrel
next prev parent reply other threads:[~2026-07-13 18:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 16:48 linux-next: build failure in final build Mark Brown
2026-07-13 18:46 ` Tyrel Datwyler [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-07-02 18:26 Mark Brown
2026-07-03 5:04 ` Kir Chou
2026-06-15 14:43 Mark Brown
2026-06-15 16:21 ` Mark Brown
2026-05-18 16:21 Mark Brown
2026-05-18 19:24 ` Nathan Chancellor
2026-05-18 20:06 ` Linus Torvalds
2026-04-01 14:07 Mark Brown
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28 2:18 ` Steven Rostedt
2026-03-26 16:04 Mark Brown
2026-03-26 17:05 ` Danilo Krummrich
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32 ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20 8:36 ` Alice Ryhl
2026-01-20 10:01 ` Danilo Krummrich
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=ae09fc06-ce41-424f-9643-5051f6256fdb@linux.ibm.com \
--to=tyreld@linux.ibm.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.