From: Vasily Tarasov <tarasov@vasily.name>
To: dm-devel@redhat.com
Cc: Joe Thornber <thornber@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Philip Shilane <philip.shilane@emc.com>,
Sonam Mandal <sonam.dp42@gmail.com>,
Erez Zadok <ezk@fsl.cs.sunysb.edu>
Subject: [PATCH RFCv2 08/10] dm-dedup: Kconfig changes
Date: Thu, 28 Aug 2014 18:12:36 -0400 [thread overview]
Message-ID: <53ffb659.a4ea320a.0d1b.16fe@mx.google.com> (raw)
Changes to Kconfig.
Signed-off-by: Vasily Tarasov <tarasov@vasily.name>
---
drivers/md/Kconfig | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
index 5bdedf6..cb9b915 100644
--- a/drivers/md/Kconfig
+++ b/drivers/md/Kconfig
@@ -432,4 +432,12 @@ config DM_SWITCH
If unsure, say N.
+config DM_DEDUP
+ tristate "Deduplication target (EXPERIMENTAL)"
+ depends on BLK_DEV_DM
+ select DM_PERSISTENT_DATA
+ select CRYPTO
+ ---help---
+ This device-maper target performs data deduplication.
+
endif # MD
--
1.7.1
reply other threads:[~2014-08-28 22:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53ffb659.a4ea320a.0d1b.16fe@mx.google.com \
--to=tarasov@vasily.name \
--cc=dm-devel@redhat.com \
--cc=ezk@fsl.cs.sunysb.edu \
--cc=hch@infradead.org \
--cc=philip.shilane@emc.com \
--cc=snitzer@redhat.com \
--cc=sonam.dp42@gmail.com \
--cc=thornber@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox