From: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Schumaker, Bryan" <Bryan.Schumaker@netapp.com>
Subject: Re: linux-next: build failure after merge of the nfs tree
Date: Wed, 16 May 2012 17:47:20 +0000 [thread overview]
Message-ID: <1337190469.3008.4.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20120516124942.5d776132d69f82bd8ed50e08@canb.auug.org.au>
On Wed, 2012-05-16 at 12:49 +1000, Stephen Rothwell wrote:
> Hi Trond,
>
> After merging the nfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/nfs/super.c: In function 'nfs_get_cache_cookie':
> fs/nfs/super.c:2361:12: error: 'struct nfs_server' has no member named 'fscache_key'
> fs/nfs/super.c:2362:16: error: 'struct nfs_server' has no member named 'fscache_key'
> fs/nfs/super.c:2363:16: error: 'struct nfs_server' has no member named 'fscache_key'
> fs/nfs/super.c:2367:2: warning: passing argument 3 of 'nfs_fscache_get_super_cookie' makes pointer from integer without a cast [enabled by default]
> fs/nfs/fscache.h:173:20: note: expected 'struct nfs_clone_mount *' but argument is of type 'int'
>
> Casued by commit 2311b9439ce8 ("NFS: Don't pass mount data to
> nfs_fscache_get_super_cookie()"). This build has CONFIG_NFS_FSCACHE
> unset. grep is your friend.
>
> I have used the nfs tree from next-20120514 for today.
>
Thanks Stephen! I've added a fix for this in todays linux-next branch.
Cheers
Trond
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2012-05-16 17:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 2:49 linux-next: build failure after merge of the nfs tree Stephen Rothwell
2012-05-16 17:47 ` Myklebust, Trond [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-04 22:53 Stephen Rothwell
2024-04-04 23:08 ` Kuniyuki Iwashima
2016-06-27 0:58 Stephen Rothwell
2016-06-27 15:44 ` Trond Myklebust
2016-06-14 0:48 Stephen Rothwell
2016-05-19 0:58 Stephen Rothwell
2016-05-19 12:06 ` Trond Myklebust
2016-05-19 17:30 ` Anna Schumaker
2016-01-08 0:14 Stephen Rothwell
2016-01-08 0:15 ` Trond Myklebust
2015-08-18 0:56 Stephen Rothwell
2015-08-19 0:05 ` Stephen Rothwell
2015-08-19 0:15 ` Drokin, Oleg
2015-08-23 23:16 ` Stephen Rothwell
2015-08-24 14:17 ` Trond Myklebust
2015-08-24 14:48 ` Oleg Drokin
2014-09-15 7:04 Stephen Rothwell
2014-09-15 17:07 ` Christoph Hellwig
2013-11-19 0:01 Stephen Rothwell
2012-10-02 0:39 Stephen Rothwell
2012-10-02 1:08 ` Myklebust, Trond
2012-03-05 0:45 Stephen Rothwell
2012-03-05 1:58 ` Myklebust, Trond
2012-01-23 0:39 Stephen Rothwell
2012-01-23 18:13 ` Trond Myklebust
2012-01-23 21:10 ` Stephen Rothwell
2011-05-27 2:08 Stephen Rothwell
2011-05-12 1:12 Stephen Rothwell
2011-05-12 15:11 ` Trond Myklebust
2011-03-11 0:22 Stephen Rothwell
2011-03-08 1:07 Stephen Rothwell
2011-03-08 18:58 ` Trond Myklebust
2010-10-21 0:38 Stephen Rothwell
2010-10-21 14:33 ` Trond Myklebust
2010-03-22 0:26 Stephen Rothwell
2010-03-22 9:49 ` Trond Myklebust
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=1337190469.3008.4.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=Bryan.Schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).