The patch titled
FUSE depends on BLOCK
has been removed from the -mm tree. Its filename was
fuse-depends-on-block.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
Subject: FUSE depends on BLOCK
From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Should FUSE depend on BLOCK? Without that and with BLOCK=n, I get:
inode.c:(.text+0x3acc5): undefined reference to `sb_set_blocksize'
inode.c:(.text+0x3a393): undefined reference to `get_sb_bdev'
fs/built-in.o:(.data+0xd718): undefined reference to `kill_block_super
Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Cc: Miklos Szeredi <miklos@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
fs/Kconfig | 1 +
1 files changed, 1 insertion(+)
diff -puN fs/Kconfig~fuse-depends-on-block fs/Kconfig
--- a/fs/Kconfig~fuse-depends-on-block
+++ a/fs/Kconfig
@@ -620,6 +620,7 @@ config AUTOFS4_FS
config FUSE_FS
tristate "Filesystem in Userspace support"
+ depends on BLOCK
help
With FUSE it is possible to implement a fully functional filesystem
in a userspace program.
_
Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are
ftape-fix-printk-format-warnings.patch
git-acpi.patch
cpufreq-select-consistently-re-2619-rc5-mm1.patch
git-ieee1394.patch
mtd-fix-printk-format-warning.patch
git-ocfs2.patch
parisc-fix-module_param-iommu-permission.patch
tifm-fix-null-ptr-and-style.patch
kconfig-printk_time-depends-on-printk.patch
fuse-depends-on-block.patch
visws-sgivwfb-is-module-needs-exports.patch
extend-notifier_call_chain-to-count-nr_calls-made-fixes.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
