From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-nfs@vger.kernel.org
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 9 (nfs)
Date: Thu, 12 Aug 2010 09:18:42 -0700 [thread overview]
Message-ID: <20100812091842.6a3b84b9.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20100809100856.b03a9bc1.randy.dunlap@oracle.com>
On Mon, 9 Aug 2010 10:08:56 -0700 Randy Dunlap wrote:
ping??
> On Mon, 9 Aug 2010 13:23:14 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > As the merge window is open, please do not add 2.6.37 material to your
> > linux-next included trees until after 2.6.36-rc1.
> >
> > Changes since 20100807:
>
>
> ERROR: "svc_gss_principal" [fs/nfs/nfs.ko] undefined!
>
>
> because in fs/nfs/Kconfig, NFS_V4 selects RPCSEC_GSS_KRB5
> and/or in fs/nfsd/Kconfig, NFSD_V4 selects RPCSEC_GSS_KRB5.
>
> RPCSEC_GSS_KRB5 does 5 selects, but none of these is enforced/followed
> by the fs/nfs[d]/Kconfig configs:
>
> select SUNRPC_GSS
> select CRYPTO
> select CRYPTO_MD5
> select CRYPTO_DES
> select CRYPTO_CBC
>
>
> Failing config is attached.
> ---
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-12 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100809132314.789e13f3.sfr@canb.auug.org.au>
2010-08-09 17:08 ` linux-next: Tree for August 9 (nfs) Randy Dunlap
2010-08-12 16:18 ` Randy Dunlap [this message]
2010-08-12 17:31 ` Trond Myklebust
2010-08-12 17:36 ` Randy Dunlap
2010-08-17 21:23 ` Trond Myklebust
[not found] ` <1282080208.12506.7.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2010-08-17 21:39 ` Randy Dunlap
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=20100812091842.6a3b84b9.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).