From: Evgeniy Polyakov <zbr@ioremap.net>
To: GregKH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org
Subject: [10/9] pohmelfs: select crypto modules from the config.
Date: Tue, 10 Feb 2009 00:30:15 +0300 [thread overview]
Message-ID: <20090209213015.GA14562@ioremap.net> (raw)
In-Reply-To: <1234188162-14727-10-git-send-email-zbr@ioremap.net>
Signed-off-by: Evgeniy Polyakov <zbr@ioremap.net>
diff --git a/drivers/staging/pohmelfs/Kconfig b/drivers/staging/pohmelfs/Kconfig
index 82d13ad..d4cbc15 100644
--- a/drivers/staging/pohmelfs/Kconfig
+++ b/drivers/staging/pohmelfs/Kconfig
@@ -1,6 +1,8 @@
config POHMELFS
tristate "POHMELFS filesystem support"
select CONNECTOR
+ select CRYPTO_BLKCIPHER
+ select CRYPTO_HMAC
help
POHMELFS stands for Parallel Optimized Host Message Exchange Layered File System.
This is a network filesystem which supports coherent caching of data and metadata
--
Evgeniy Polyakov
next prev parent reply other threads:[~2009-02-09 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 14:02 [0/9] pohmelfs for drivers/staging Evgeniy Polyakov
2009-02-09 14:02 ` [1/9] pohmelfs: documentation Evgeniy Polyakov
2009-02-09 14:02 ` [2/9] pohmelfs: configuration interface Evgeniy Polyakov
2009-02-09 14:02 ` [3/9] pohmelfs: crypto processing Evgeniy Polyakov
2009-02-09 14:02 ` [4/9] pohmelfs: directory operations Evgeniy Polyakov
2009-02-09 14:02 ` [5/9] pohmelfs: inode operations Evgeniy Polyakov
2009-02-09 14:02 ` [6/9] pohmelfs: distributed locking and cache coherency protocol Evgeniy Polyakov
2009-02-09 14:02 ` [7/9] pohmelfs: network operations Evgeniy Polyakov
2009-02-09 14:02 ` [8/9] pohmelfs: transaction layer Evgeniy Polyakov
2009-02-09 14:02 ` [9/9] pohmelfs: kconfig/makefile and vfs changes Evgeniy Polyakov
2009-02-09 21:30 ` Evgeniy Polyakov [this message]
2009-02-12 19:41 ` [0/9] pohmelfs for drivers/staging Greg KH
2009-02-12 20:58 ` Evgeniy Polyakov
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=20090209213015.GA14562@ioremap.net \
--to=zbr@ioremap.net \
--cc=greg@kroah.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.