From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: Unable to build branch nvme-5.18
Date: Wed, 23 Mar 2022 22:26:31 +0000 [thread overview]
Message-ID: <ddf69f88-480e-a05f-da06-ed106926769c@nvidia.com> (raw)
In-Reply-To: <SJ0PR19MB45446560EB7A86ABFFA6BA9FF2189@SJ0PR19MB4544.namprd19.prod.outlook.com>
On 3/23/22 12:32, Belanger, Martin wrote:
> I tried to build branch nvme-5.18 on Fedora 35, but I get this error:
>
> LDS scripts/module.lds
> MODPOST modules-only.symvers
> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-tcp.ko] undefined!
> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvme-fcloop.ko] undefined!
> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined!
> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-rdma.ko] undefined!
> ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvme-loop.ko] undefined!
> make[1]: *** [scripts/Makefile.modpost:134: modules-only.symvers] Error 1
> make[1]: *** Deleting file 'modules-only.symvers'
> make: *** [Makefile:1746: modules] Error 2
>
> Any thoughts?
>
this should work :-
diff --git a/drivers/nvme/target/core.c b/drivers/nvme/target/core.c
index 8f3762f4450f..7c17a9d79da1 100644
--- a/drivers/nvme/target/core.c
+++ b/drivers/nvme/target/core.c
@@ -18,6 +18,7 @@
struct workqueue_struct *buffered_io_wq;
struct workqueue_struct *zbd_wq;
struct workqueue_struct *nvmet_wq;
+EXPORT_SYMBOL_GPL(nvmet_wq);
static const struct nvmet_fabrics_ops *nvmet_transports[NVMF_TRTYPE_MAX];
static DEFINE_IDA(cntlid_ida);
> Thanks,
> Martin
>
next prev parent reply other threads:[~2022-03-23 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 19:32 Unable to build branch nvme-5.18 Belanger, Martin
2022-03-23 22:26 ` Chaitanya Kulkarni [this message]
2022-03-24 10:57 ` Sagi Grimberg
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=ddf69f88-480e-a05f-da06-ed106926769c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
/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