From: "J. Bruce Fields" <bfields@fieldses.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-nfs@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, Neil Brown <neilb@suse.de>
Subject: Re: linux-next: Tree for March 16 (nfsd)
Date: Wed, 16 Mar 2011 12:44:53 -0400 [thread overview]
Message-ID: <20110316164453.GB9299@fieldses.org> (raw)
In-Reply-To: <20110316093234.a82a8b0b.randy.dunlap@oracle.com>
On Wed, Mar 16, 2011 at 09:32:34AM -0700, Randy Dunlap wrote:
> On Wed, 16 Mar 2011 19:14:44 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110315:
>
>
> ERROR: "gss_mech_put" [fs/nfsd/nfsd.ko] undefined!
> ERROR: "gss_mech_get_by_name" [fs/nfsd/nfsd.ko] undefined!
Let me know if this is not fixed by
0a5e5f122c756d1c1a6ca712eda76ea8664e5fd9 in the latest
git://linux-nfs.org/~bfields/linux.git for-2.6.39
--b.
next prev parent reply other threads:[~2011-03-16 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 8:14 linux-next: Tree for March 16 Stephen Rothwell
2011-03-16 16:32 ` linux-next: Tree for March 16 (nfsd) Randy Dunlap
2011-03-16 16:44 ` J. Bruce Fields [this message]
2011-03-16 18:38 ` [PATCH -next] i2c: designware-pcidrv depends on PCI 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=20110316164453.GB9299@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=randy.dunlap@oracle.com \
--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).