From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org, linux-nvme@lists.infradead.org,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [linux-nvme:nvme-5.18 4/5] ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined!
Date: Wed, 23 Mar 2022 17:33:52 +0100 [thread overview]
Message-ID: <20220323163352.GA1560@lst.de> (raw)
In-Reply-To: <9c747632-2cd0-3096-40d8-e3df40b95679@grimberg.me>
On Wed, Mar 23, 2022 at 06:33:13PM +0200, Sagi Grimberg wrote:
> --- 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);
> --
>
> Christoph, can you fold it in or should I?
I'll fold it in.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: kbuild-all@lists.01.org
Subject: Re: [linux-nvme:nvme-5.18 4/5] ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined!
Date: Wed, 23 Mar 2022 17:33:52 +0100 [thread overview]
Message-ID: <20220323163352.GA1560@lst.de> (raw)
In-Reply-To: <9c747632-2cd0-3096-40d8-e3df40b95679@grimberg.me>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Wed, Mar 23, 2022 at 06:33:13PM +0200, Sagi Grimberg wrote:
> --- 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);
> --
>
> Christoph, can you fold it in or should I?
I'll fold it in.
next prev parent reply other threads:[~2022-03-23 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:20 [linux-nvme:nvme-5.18 4/5] ERROR: modpost: "nvmet_wq" [drivers/nvme/target/nvmet-fc.ko] undefined! kernel test robot
2022-03-23 16:33 ` Sagi Grimberg
2022-03-23 16:33 ` Sagi Grimberg
2022-03-23 16:33 ` Christoph Hellwig [this message]
2022-03-23 16:33 ` Christoph Hellwig
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=20220323163352.GA1560@lst.de \
--to=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=lkp@intel.com \
--cc=sagi@grimberg.me \
/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.