Commit a3b2e093 authored by Greg Kroah-Hartman's avatar Greg Kroah-Hartman

Staging: add cowloop to the build

Now that the code can build, let's add it to the build system.

Cc: "H.J. Thomassen" <hjt@ATComputing.nl>
Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
parent 5cc06df6
......@@ -141,5 +141,7 @@ source "drivers/staging/sep/Kconfig"
source "drivers/staging/iio/Kconfig"
source "drivers/staging/cowloop/Kconfig"
endif # !STAGING_EXCLUDE_BUILD
endif # STAGING
......@@ -52,3 +52,4 @@ obj-$(CONFIG_VME_BUS) += vme/
obj-$(CONFIG_RAR_REGISTER) += rar/
obj-$(CONFIG_DX_SEP) += sep/
obj-$(CONFIG_IIO) += iio/
obj-$(CONFIG_COWLOOP) += cowloop/
config COWLOOP
tristate "copy-on-write pseudo Block Driver"
depends on BLOCK
default n
---help---
Cowloop is a "copy-on-write" pseudo block driver. It can be
stacked on top of a "real" block driver, and catches all write
operations on their way from the file systems layer above to
the real driver below, effectively shielding the lower driver
from those write accesses. The requests are then diverted to
an ordinary file, located somewhere else (configurable). Later
read requests are checked to see whether they can be serviced
by the "real" block driver below, or must be pulled in from
the diverted location. More information and userspace tools to
use the driver are on the project's website
http://www.ATComputing.nl/cowloop/
obj-$(CONFIG_COWLOOP) += cowloop.o
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