Commit b9f5fb18 authored by Arnd Bergmann's avatar Arnd Bergmann Committed by Linus Torvalds

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: 99c18ce5 ("cramfs: direct memory access support")
Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
Signed-off-by: default avatarNicolas Pitre <nico@linaro.org>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 73d080d3
...@@ -34,6 +34,7 @@ config CRAMFS_BLOCKDEV ...@@ -34,6 +34,7 @@ config CRAMFS_BLOCKDEV
config CRAMFS_MTD config CRAMFS_MTD
bool "Support CramFs image directly mapped in physical memory" bool "Support CramFs image directly mapped in physical memory"
depends on CRAMFS && MTD depends on CRAMFS && MTD
depends on CRAMFS=m || MTD=y
default y if !CRAMFS_BLOCKDEV default y if !CRAMFS_BLOCKDEV
help help
This option allows the CramFs driver to load data directly from This option allows the CramFs driver to load data directly from
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment