From: Michael Halcrow <mhalcrow@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
LKML <linux-kernel@vger.kernel.org>,
trevor.highland@gmail.com, tyhicks@ou.edu
Subject: Re: [PATCH 1/2] eCryptfs: Public key; transport mechanism
Date: Tue, 12 Dec 2006 10:54:16 -0600 [thread overview]
Message-ID: <20061212165416.GA4796@us.ibm.com> (raw)
In-Reply-To: <20061209112130.f3ba7f22.akpm@osdl.org>
On Sat, Dec 09, 2006 at 11:21:30AM -0800, Andrew Morton wrote:
> On Sat, 9 Dec 2006 11:04:16 -0800
> Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > > ecryptfs now has a dependency upon netlink. There's no
> > > CONFIG_NETLINK. If CONFIG_NET=n && CONFIG_ECRYPTFS=y is
> > > possible, it won't build.
> >
> > Then shouldn't ECRYPTFS depend on CONFIG_NET ?
>
> yup, that's what I meant..
Add net build dependency to eCryptfs Kconfig entry.
Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>
---
fs/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
b2bc2515b6849154a9598bca4975dc721799954c
diff --git a/fs/Kconfig b/fs/Kconfig
index c93d82b..17ae291 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -1103,7 +1103,7 @@ config AFFS_FS
config ECRYPT_FS
tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
- depends on EXPERIMENTAL && KEYS && CRYPTO
+ depends on EXPERIMENTAL && KEYS && CRYPTO && NET
help
Encrypted filesystem that operates on the VFS layer. See
<file:Documentation/ecryptfs.txt> to learn more about
--
1.3.3
prev parent reply other threads:[~2006-12-12 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 23:06 [PATCH 1/2] eCryptfs: Public key; transport mechanism Michael Halcrow
2006-12-06 23:12 ` [PATCH 2/2] eCryptfs: Public key; packet management Michael Halcrow
2006-12-07 5:57 ` Andrew Morton
2006-12-07 5:55 ` [PATCH 1/2] eCryptfs: Public key; transport mechanism Andrew Morton
2006-12-07 16:06 ` Michael Halcrow
2006-12-09 19:04 ` Randy Dunlap
2006-12-09 19:21 ` Andrew Morton
2006-12-09 19:50 ` Randy Dunlap
2006-12-12 16:54 ` Michael Halcrow [this message]
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=20061212165416.GA4796@us.ibm.com \
--to=mhalcrow@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=trevor.highland@gmail.com \
--cc=tyhicks@ou.edu \
/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.