[lkml]   [2017]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH] 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 <>
    fs/cramfs/Kconfig | 1 +
    1 file changed, 1 insertion(+)

    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
    This option allows the CramFs driver to load data directly from
     \ /
      Last update: 2017-11-10 15:58    [W:4.233 / U:0.160 seconds]
    ©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site