In the case of lustre routers you only need a functioning
LNet stack. Especially since often the routers are very
light weight and want to avoid any addition software that
would create additional pressures on the system.
Signed-off-by: James Simmons <jsimmons@infradead.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 obj-$(CONFIG_LTE_GDM724X)      += gdm724x/
 obj-$(CONFIG_FIREWIRE_SERIAL)  += fwserial/
 obj-$(CONFIG_GOLDFISH)         += goldfish/
-obj-$(CONFIG_LUSTRE_FS)                += lustre/
+obj-$(CONFIG_LNET)             += lustre/
 obj-$(CONFIG_DGNC)                     += dgnc/
 obj-$(CONFIG_MTD_SPINAND_MT29F)        += mt29f_spinand/
 obj-$(CONFIG_GS_FPGABOOT)      += gs_fpgaboot/
 
-source "drivers/staging/lustre/lustre/Kconfig"
-
 source "drivers/staging/lustre/lnet/Kconfig"
+
+source "drivers/staging/lustre/lustre/Kconfig"
 
 config LNET
        tristate "Lustre networking subsystem (LNet)"
-       depends on LUSTRE_FS
+       depends on INET && m
        help
          The Lustre network layer, also known as LNet, is a networking abstaction
          level API that was initially created to allow Lustre Filesystem to utilize
 
 config LUSTRE_FS
        tristate "Lustre file system client support"
-       depends on INET && m && !MIPS && !XTENSA && !SUPERH
+       depends on m && !MIPS && !XTENSA && !SUPERH
        select LNET
        select CRYPTO
        select CRYPTO_CRC32