From: Randy Dunlap <randy.dunlap@oracle.com>
To: Shirish Pargaonkar <shirishpargaonkar@gmail.com>
Cc: Suresh Jayaraman <sjayaraman@suse.de>,
Miguel Calleja <mcalleja1@telecable.es>,
LKML <linux-kernel@vger.kernel.org>,
linux-cifs@vger.kernel.org,
Shirish S Pargaonkar <shirishp@us.ibm.com>
Subject: Re: Linux 2.6.36-rc3
Date: Mon, 30 Aug 2010 10:25:27 -0700 [thread overview]
Message-ID: <20100830102527.17d5e1f1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <AANLkTi=S3E80edLwAAAOwehrakYVgeKzC+yKptwJJZLc@mail.gmail.com>
On Mon, 30 Aug 2010 12:14:53 -0500 Shirish Pargaonkar wrote:
> On Mon, Aug 30, 2010 at 12:00 PM, Suresh Jayaraman <sjayaraman@suse.de> wrote:
> > (Cc linux-cifs@vger.kernel.org)
> >
> > Couldn't get a chance to check this, but I guess this is perhaps due to
> > the recent crypto patches..
>
> Suresh, yes, cifs auth and signing code using kernel crypto (shash) apis.
>
> fs/cifs/Kconfig
>
> select CRYPTO_MD5
> select CRYPTO_ARC4
>
Either CIFS should depend on CRYPTO:
change
depends on INET
to
depends on INET && CRYPTO
or it can also select CRYPTO.
>
> >
> > On 08/30/2010 02:17 PM, Miguel Calleja wrote:
> >> CIFS does not build without CRYPTO selected.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-30 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinRRiW1VUzS+3T82=q8PsoRn78Cgn_X8gSduM0U@mail.gmail.com>
[not found] ` <i5fr6h$ih6$1@dough.gmane.org>
2010-08-30 17:00 ` Linux 2.6.36-rc3 Suresh Jayaraman
[not found] ` <4C7BE3AE.8020204-l3A5Bk7waGM@public.gmane.org>
2010-08-30 17:14 ` Shirish Pargaonkar
2010-08-30 17:25 ` Randy Dunlap [this message]
[not found] ` <20100830102527.17d5e1f1.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-08-30 21:27 ` Steve French
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=20100830102527.17d5e1f1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcalleja1@telecable.es \
--cc=shirishp@us.ibm.com \
--cc=shirishpargaonkar@gmail.com \
--cc=sjayaraman@suse.de \
/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