From: Stephen Rothwell <sfr@au1.ibm.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: build failure after merge of the nfs tree
Date: Thu, 12 May 2011 11:12:55 +1000 [thread overview]
Message-ID: <20110512111255.95a765aa.sfr@au.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Hi Trond,
After merging the nfs tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/nfs/write.c: In function 'nfs_flush_multi':
fs/nfs/write.c:942: error: too many arguments to function 'pnfs_update_layout'
fs/nfs/write.c: In function 'nfs_flush_one':
fs/nfs/write.c:1016: error: too many arguments to function 'pnfs_update_layout'
fs/nfs/read.c: In function 'nfs_pagein_multi':
fs/nfs/read.c:291: error: too many arguments to function 'pnfs_update_layout'
fs/nfs/read.c: In function 'nfs_pagein_one':
fs/nfs/read.c:354: error: too many arguments to function 'pnfs_update_layout'
Cased by commit 4b386a0fe47b ("NFSv4.1: Ensure that layoutget uses the
correct gfp modes") which forgot to update the function declaration for
the !CONFIG_NFS_V4_1 case.
I have used the nfs tree from next-20110511 for today.
--
Cheers,
Stephen Rothwell sfr@au.ibm.com
IBM OzLabs Linux Technology Centre
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-05-12 1:13 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 1:12 Stephen Rothwell [this message]
2011-05-12 15:11 ` linux-next: build failure after merge of the nfs tree Trond Myklebust
-- 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-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=20110512111255.95a765aa.sfr@au.ibm.com \
--to=sfr@au1.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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