From: Trond Myklebust <trond.myklebust@fys•uio.no>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Frank Filz <ffilzlnx@us•ibm.com>,
Jeff Layton <jlayton@redhat•com>
Subject: Re: linux-next: build failure after merge of the nfs tree
Date: Tue, 08 Mar 2011 13:58:31 -0500 [thread overview]
Message-ID: <1299610712.3602.15.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20110308120753.8adb3ff6.sfr@canb.auug.org.au>
On Tue, 2011-03-08 at 12:07 +1100, Stephen Rothwell wrote:
> Hi Trond,
>
> After merging the nfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> fs/nfs/inode.c: In function 'nfs_compat_user_ino64':
> fs/nfs/inode.c:93: error: 'compat_ulong_t' undeclared (first use in this function)
> fs/nfs/inode.c:93: error: expected ';' before 'ino'
> fs/nfs/inode.c:100: error: 'ino' undeclared (first use in this function)
>
> Caused by commit 5fa1ca22302da56ffa568e847100e80be90cc602 ("(try3-resend)
> Fix nfs_compat_user_ino64 so it doesn't cause problems if bit 31 or 63
> are set in fileid").
>
> I have used the nfs tree from next-20110307 for today.
Thanks Stephen!
It looks to me as if we need to add a '#include <compat.h>'. I'll fix up
the patch...
Cheers
Trond
next prev parent reply other threads:[~2011-03-08 19:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 1:07 linux-next: build failure after merge of the nfs tree Stephen Rothwell
2011-03-08 18:58 ` Trond Myklebust [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-05-16 2:49 Stephen Rothwell
2012-05-16 17:47 ` 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
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=1299610712.3602.15.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys$(echo .)uio.no \
--cc=ffilzlnx@us$(echo .)ibm.com \
--cc=jlayton@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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