From: Hannes Reinecke <hare@suse.de>
To: Jens Axboe <axboe@kernel.dk>,
Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>,
linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, abdhalee@linux.vnet.ibm.com,
sachinp@linux.vnet.com, mputtash@linux.vnet.com,
Christoph Hellwig <hch@lst.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [linux-next] build fails modpost: "blkcg_get_fc_appid" [drivers/nvme/host/nvme-fc.ko] undefined!
Date: Thu, 19 May 2022 14:38:23 +0200 [thread overview]
Message-ID: <fc5f8b96-3c93-5400-b917-a1d991cbe7c9@suse.de> (raw)
In-Reply-To: <7b16694b-0281-d06d-7564-c4f26760a25e@kernel.dk>
On 5/19/22 14:14, Jens Axboe wrote:
> On 5/19/22 1:49 AM, Tasmiya Nalatwad wrote:
>> Greetings,
>>
>> linux-next build fails modpost: "blkcg_get_fc_appid" [drivers/nvme/host/nvme-fc.ko] undefined!
>>
>> Console Logs :
>>
>> [console-expect]#make -j 17 -s && make modules && make modules_install && make install
>> make -j 17 -s && make modules && make modules_install && make install
>> ERROR: modpost: "blkcg_get_fc_appid" [drivers/nvme/host/nvme-fc.ko] undefined!
>> make[1]: *** [scripts/Makefile.modpost:134: modules-only.symvers] Error 1
>> make: *** [Makefile:1914: modules] Error 2
>> make: *** Waiting for unfinished jobs....
>
> Christoph, can you fix this up?
>
Cannot reproduce with commit 21498d01d045c5b95b93e0a0625ae965b4330ebe.
Please share details.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), GF: Felix Imendörffer
next prev parent reply other threads:[~2022-05-19 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 7:49 Tasmiya Nalatwad
2022-05-19 12:14 ` Jens Axboe
2022-05-19 12:38 ` Hannes Reinecke [this message]
2022-05-19 12:40 ` Jens Axboe
2022-05-19 12:42 ` Jens Axboe
2022-05-19 13:02 ` Hannes Reinecke
2022-05-19 20:02 ` Randy Dunlap
2022-05-20 6:33 ` Hannes Reinecke
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=fc5f8b96-3c93-5400-b917-a1d991cbe7c9@suse.de \
--to=hare@suse.de \
--cc=abdhalee@linux.vnet.ibm.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mputtash@linux.vnet.com \
--cc=sachinp@linux.vnet.com \
--cc=tasmiya@linux.vnet.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®