From: Jody Bruchon <jody-CwlhuK3P8e+1Z/+hSey0Gg@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] fs/cifs/Kconfig: CIFS depends on CRYPTO_HMAC
Date: Sat, 13 Nov 2010 15:09:04 -0500 [thread overview]
Message-ID: <4CDEF060.2050000@nctritech.com> (raw)
I sent this patch in to LKML, but later realized it should probably go
here. I don't subscribe to the list, so please CC me directly with any
replies. Thanks!
Jody Bruchon
-------- Original Message --------
Subject: [PATCH] fs/cifs/Kconfig: CIFS depends on CRYPTO_HMAC
Date: Fri, 12 Nov 2010 13:41:06 -0500
From: Jody Bruchon <jody-CwlhuK3P8e+1Z/+hSey0Gg@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
linux-2.6.37-rc1: I compiled a kernel with CIFS which subsequently
failed with an error indicating it couldn't initialize crypto module
"hmacmd5". CONFIG_CRYPTO_HMAC=y fixed the problem.
This patch makes CIFS depend on CRYPTO_HMAC in kconfig.
Signed-off-by: Jody Bruchon<jody-CwlhuK3P8e+1Z/+hSey0Gg@public.gmane.org>
---
diff -Naur linux-2.6.37-rc1/fs/cifs/Kconfig b/fs/cifs/Kconfig
--- linux-2.6.37-rc1/fs/cifs/Kconfig 2010-11-12 13:22:31.742999981 -0500
+++ b/fs/cifs/Kconfig 2010-11-12 13:22:27.528998658 -0500
@@ -4,6 +4,7 @@
select NLS
select CRYPTO
select CRYPTO_MD5
+ select CRYPTO_HMAC
select CRYPTO_ARC4
help
This is the client VFS module for the Common Internet File System
next reply other threads:[~2010-11-13 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-13 20:09 Jody Bruchon [this message]
[not found] ` <4CDEF060.2050000-CwlhuK3P8e+1Z/+hSey0Gg@public.gmane.org>
2010-11-14 3:37 ` [PATCH] fs/cifs/Kconfig: CIFS depends on CRYPTO_HMAC Steve French
2010-11-14 3:37 ` Steve French
-- strict thread matches above, loose matches on Subject: below --
2010-11-12 18:41 Jody Bruchon
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=4CDEF060.2050000@nctritech.com \
--to=jody-cwlhuk3p8e+1z/+hsey0gg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.