From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
linux-kbuild@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-s390@vger.kernel.org, Stefan Haberland <sth@linux.ibm.com>,
Jan Hoeppner <hoeppner@linux.ibm.com>
Subject: linux-next-2023-0815: s390/block/dasd: build error
Date: Tue, 15 Aug 2023 22:34:19 -0700 [thread overview]
Message-ID: <95b176a2-3670-1e89-c8f6-86b094eebc4c@infradead.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
I have spent some time on this but I don't see where the problem is.
ERROR: modpost: "bdev_mark_dead" [drivers/s390/block/dasd_mod.ko] undefined!
CONFIG_BLOCK=y, bdev.o is built and contains the missing symbol.
Full randconfig file is attached.
Hopefully I'm just overlooking something.
~Randy
[-- Attachment #2: config-r5177.gz --]
[-- Type: application/gzip, Size: 19900 bytes --]
next reply other threads:[~2023-08-16 5:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 5:34 Randy Dunlap [this message]
2023-08-16 7:03 ` Sven Schnelle
2023-08-16 7:14 ` Stephen Rothwell
2023-08-16 8:11 ` Christian Brauner
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=95b176a2-3670-1e89-c8f6-86b094eebc4c@infradead.org \
--to=rdunlap@infradead.org \
--cc=hoeppner@linux.ibm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=sth@linux.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®