mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, tyhicks@linux.vnet.ibm.com
Subject: Re: [to-be-updated] ecryptfs-depends-on-crypto.patch removed from -mm tree
Date: Mon, 28 Sep 2009 17:22:54 -0700	[thread overview]
Message-ID: <20090928172254.bca66f54.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200909290018.n8T0IU8X020007@imap1.linux-foundation.org>

On Mon, 28 Sep 2009 17:18:30 -0700 akpm@linux-foundation.org wrote:

> 
> The patch titled
>      ecryptfs: depends on CRYPTO
> has been removed from the -mm tree.  Its filename was
>      ecryptfs-depends-on-crypto.patch
> 
> This patch was dropped because an updated version will be merged

what updated version?  hm, we'll see.


> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
> 
> ------------------------------------------------------
> Subject: ecryptfs: depends on CRYPTO
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> ecryptfs uses crypto APIs so it should depend on CRYPTO.
> Otherwise many build errors occur. [63 lines not pasted]
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> Cc: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
> 
>  fs/ecryptfs/Kconfig |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff -puN fs/ecryptfs/Kconfig~ecryptfs-depends-on-crypto fs/ecryptfs/Kconfig
> --- a/fs/ecryptfs/Kconfig~ecryptfs-depends-on-crypto
> +++ a/fs/ecryptfs/Kconfig
> @@ -1,6 +1,6 @@
>  config ECRYPT_FS
>  	tristate "eCrypt filesystem layer support (EXPERIMENTAL)"
> -	depends on EXPERIMENTAL && KEYS && NET
> +	depends on EXPERIMENTAL && KEYS && NET && CRYPTO
>  	select CRYPTO_ECB
>  	select CRYPTO_CBC
>  	help


---
~Randy

           reply	other threads:[~2009-09-29  0:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200909290018.n8T0IU8X020007@imap1.linux-foundation.org>]

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=20090928172254.bca66f54.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tyhicks@linux.vnet.ibm.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

Powered by JetHome