linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH next] Staging: pohmelfs should depend on CRYPTO
@ 2009-02-13 15:06 Alexander Beregalov
  2009-02-14 10:27 ` Evgeniy Polyakov
  0 siblings, 1 reply; 3+ messages in thread
From: Alexander Beregalov @ 2009-02-13 15:06 UTC (permalink / raw)
  To: zbr, gregkh, linux-next, linux-kernel



Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
---

 drivers/staging/pohmelfs/Kconfig |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/staging/pohmelfs/Kconfig b/drivers/staging/pohmelfs/Kconfig
index f150ecb..4c6276b 100644
--- a/drivers/staging/pohmelfs/Kconfig
+++ b/drivers/staging/pohmelfs/Kconfig
@@ -1,6 +1,7 @@
 config POHMELFS
 	tristate "POHMELFS filesystem support"
 	select CONNECTOR
+	select CRYPTO
 	select CRYPTO_BLKCIPHER
 	select CRYPTO_HMAC
 	help

^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH next] Staging: pohmelfs should depend on CRYPTO
  2009-02-13 15:06 [PATCH next] Staging: pohmelfs should depend on CRYPTO Alexander Beregalov
@ 2009-02-14 10:27 ` Evgeniy Polyakov
  2009-02-14 11:00   ` Alexander Beregalov
  0 siblings, 1 reply; 3+ messages in thread
From: Evgeniy Polyakov @ 2009-02-14 10:27 UTC (permalink / raw)
  To: Alexander Beregalov; +Cc: gregkh, linux-next, linux-kernel

On Fri, Feb 13, 2009 at 06:06:54PM +0300, Alexander Beregalov (a.beregalov@gmail.com) wrote:
> 
> 
> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>

Doesn't subsystem selection also forces higher level selection, i.e.
selecing CRYPTO_BLKCIPHER also forces CRYPTO selection? If it is not the
case, then your patch is definitely valid.

> ---
> 
>  drivers/staging/pohmelfs/Kconfig |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/staging/pohmelfs/Kconfig b/drivers/staging/pohmelfs/Kconfig
> index f150ecb..4c6276b 100644
> --- a/drivers/staging/pohmelfs/Kconfig
> +++ b/drivers/staging/pohmelfs/Kconfig
> @@ -1,6 +1,7 @@
>  config POHMELFS
>  	tristate "POHMELFS filesystem support"
>  	select CONNECTOR
> +	select CRYPTO
>  	select CRYPTO_BLKCIPHER
>  	select CRYPTO_HMAC
>  	help

-- 
	Evgeniy Polyakov

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH next] Staging: pohmelfs should depend on CRYPTO
  2009-02-14 10:27 ` Evgeniy Polyakov
@ 2009-02-14 11:00   ` Alexander Beregalov
  0 siblings, 0 replies; 3+ messages in thread
From: Alexander Beregalov @ 2009-02-14 11:00 UTC (permalink / raw)
  To: Evgeniy Polyakov; +Cc: gregkh, linux-next, linux-kernel

2009/2/14 Evgeniy Polyakov <zbr@ioremap.net>:
> On Fri, Feb 13, 2009 at 06:06:54PM +0300, Alexander Beregalov (a.beregalov@gmail.com) wrote:
>>
>>
>> Signed-off-by: Alexander Beregalov <a.beregalov@gmail.com>
>
> Doesn't subsystem selection also forces higher level selection, i.e.
> selecing CRYPTO_BLKCIPHER also forces CRYPTO selection? If it is not the
> case, then your patch is definitely valid.
No, it does not. The kernel fails to build if CRYPTO was disabled
before enabling POHMELFS.
>
>> ---
>>
>>  drivers/staging/pohmelfs/Kconfig |    1 +
>>  1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/staging/pohmelfs/Kconfig b/drivers/staging/pohmelfs/Kconfig
>> index f150ecb..4c6276b 100644
>> --- a/drivers/staging/pohmelfs/Kconfig
>> +++ b/drivers/staging/pohmelfs/Kconfig
>> @@ -1,6 +1,7 @@
>>  config POHMELFS
>>       tristate "POHMELFS filesystem support"
>>       select CONNECTOR
>> +     select CRYPTO
>>       select CRYPTO_BLKCIPHER
>>       select CRYPTO_HMAC
>>       help
>
> --
>        Evgeniy Polyakov
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-02-14 11:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-13 15:06 [PATCH next] Staging: pohmelfs should depend on CRYPTO Alexander Beregalov
2009-02-14 10:27 ` Evgeniy Polyakov
2009-02-14 11:00   ` Alexander Beregalov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).