From: Hannes Reinecke <hare@suse.de>
To: Randy Dunlap <rdunlap@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Tasmiya Nalatwad <tasmiya@linux.vnet.ibm.com>,
linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Abdul Haleem <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>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [linux-next] build fails modpost: "blkcg_get_fc_appid" [drivers/nvme/host/nvme-fc.ko] undefined!
Date: Fri, 20 May 2022 08:33:26 +0200 [thread overview]
Message-ID: <eabd386f-9e25-b05c-654e-2b3da0217634@suse.de> (raw)
In-Reply-To: <6f38a339-41b5-aafe-c788-bd34a1806d52@infradead.org>
On 5/19/22 13:02, Randy Dunlap wrote:
>
>
> On 5/19/22 06:02, Hannes Reinecke wrote:
>> On 5/19/22 14:42, Jens Axboe wrote:
>>> On 5/19/22 6:40 AM, Jens Axboe wrote:
>>>> On Thu, May 19, 2022 at 6:38 AM Hannes Reinecke <hare@suse.de> wrote:
>>>>>
>>>>> 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.
>>>>
>>>> The kerneltest bot also reported this a few days ago, you might be able
>>>> to find the details there as that includes config etc.
>>>
>>> Here: https://lore.kernel.org/linux-mm/202205190527.o9wVEvHI-lkp@intel.com/
>>>
>> Right. Send a patch.
>
>
> https://lore.kernel.org/all/20220518045704.GA30131@lst.de/
>
> but it needs to be sent as a formal patch.
>
I am confused.
The 'for-next' branch from Martin Petersen has the updated patch
(827fc630e4c8 ("scsi: nvme-fc: Add new routine nvme_fc_io_getuuid()")
but linux-next is still on the old (v1) version.
Not sure what to do here.
Martin?
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
prev parent reply other threads:[~2022-05-20 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86768c9d-9a9c-653b-ab99-86de3bc434d8@linux.vnet.ibm.com>
2022-05-19 12:14 ` [linux-next] build fails modpost: "blkcg_get_fc_appid" [drivers/nvme/host/nvme-fc.ko] undefined! Jens Axboe
2022-05-19 12:38 ` Hannes Reinecke
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 [this message]
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=eabd386f-9e25-b05c-654e-2b3da0217634@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=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mputtash@linux.vnet.com \
--cc=rdunlap@infradead.org \
--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