diff options
| author | Arnd Bergmann <arnd@arndb.de> | 2017-11-10 15:57:21 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-12-17 12:20:58 -0800 |
| commit | b9f5fb1800d8a4a3bc6cd3152c5f3d252986cf79 (patch) | |
| tree | 25509d31942911a9b3bc9f4278939e140209ee9e /fs/cramfs | |
| parent | 73d080d374a509ae887b8a0744ad4d553c5d5d24 (diff) | |
| download | lwn-b9f5fb1800d8a4a3bc6cd3152c5f3d252986cf79.tar.gz lwn-b9f5fb1800d8a4a3bc6cd3152c5f3d252986cf79.zip | |
cramfs: fix MTD dependency
With CONFIG_MTD=m and CONFIG_CRAMFS=y, we now get a link failure:
fs/cramfs/inode.o: In function `cramfs_mount': inode.c:(.text+0x220): undefined reference to `mount_mtd'
fs/cramfs/inode.o: In function `cramfs_mtd_fill_super':
inode.c:(.text+0x6d8): undefined reference to `mtd_point'
inode.c:(.text+0xae4): undefined reference to `mtd_unpoint'
This adds a more specific Kconfig dependency to avoid the broken
configuration.
Alternatively we could make CRAMFS itself depend on "MTD || !MTD" with a
similar result.
Fixes: 99c18ce580c6 ("cramfs: direct memory access support")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Nicolas Pitre <nico@linaro.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/cramfs')
| -rw-r--r-- | fs/cramfs/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/cramfs/Kconfig b/fs/cramfs/Kconfig index f937082f3244..58e2fe40b2a0 100644 --- a/fs/cramfs/Kconfig +++ b/fs/cramfs/Kconfig @@ -34,6 +34,7 @@ config CRAMFS_BLOCKDEV config CRAMFS_MTD bool "Support CramFs image directly mapped in physical memory" depends on CRAMFS && MTD + depends on CRAMFS=m || MTD=y default y if !CRAMFS_BLOCKDEV help This option allows the CramFs driver to load data directly from |