kernel-fxtec-pro1x/fs/exofs/Kconfig.ore

# ORE - Objects Raid Engine (libore.ko)
#
# Note ORE needs to "select ASYNC_XOR". So Not to force multiple selects
# for every ORE user we do it like this. Any user should add itself here
# at the "depends on EXOFS_FS || ..." with an ||. The dependencies are
# selected here, and we default to "ON". So in effect it is like been
# selected by any of the users.
config ORE
	tristate
	depends on EXOFS_FS || PNFS_OBJLAYOUT
	select ASYNC_XOR
	default SCSI_OSD_ULD
ore: FIX breakage when MISC_FILESYSTEMS is not set As Reported by Randy Dunlap When MISC_FILESYSTEMS is not enabled and NFS4.1 is: fs/built-in.o: In function `objio_alloc_io_state': objio_osd.c:(.text+0xcb525): undefined reference to `ore_get_rw_state' fs/built-in.o: In function `_write_done': objio_osd.c:(.text+0xcb58d): undefined reference to `ore_check_io' fs/built-in.o: In function `_read_done': ... When MISC_FILESYSTEMS, which is more of a GUI thing then anything else, is not selected. exofs/Kconfig is never examined during Kconfig, and it can not do it's magic stuff to automatically select everything needed. We must split exofs/Kconfig in two. The ore one is always included. And the exofs one is left in it's old place in the menu. [Needed for the 3.2.0 Kernel] CC: Stable Tree <stable@kernel.org> Reported-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Boaz Harrosh <bharrosh@panasas.com> 2011-11-29 16:35:53 -07:00			`# ORE - Objects Raid Engine (libore.ko)`
			`#`
			`# Note ORE needs to "select ASYNC_XOR". So Not to force multiple selects`
			`# for every ORE user we do it like this. Any user should add itself here`
			`# at the "depends on EXOFS_FS \|\| ..." with an \|\|. The dependencies are`
			`# selected here, and we default to "ON". So in effect it is like been`
			`# selected by any of the users.`
			`config ORE`
			`tristate`
			`depends on EXOFS_FS \|\| PNFS_OBJLAYOUT`
			`select ASYNC_XOR`
			`default SCSI_OSD_ULD`