From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Trond Myklebust <trond.myklebust@fys•uio.no>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Bryan Schumaker <bjschuma@netapp•com>
Subject: linux-next: build failure after merge of the final tree (nfs tree related)
Date: Thu, 30 Sep 2010 13:58:34 +1000 [thread overview]
Message-ID: <20100930135834.dc73dfac.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
Hi Trond,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
fs/nfs/idmap.c: In function 'nfs_idmap_init':
fs/nfs/idmap.c:79: error: implicit declaration of function 'IS_ERR'
fs/nfs/idmap.c:80: error: implicit declaration of function 'PTR_ERR'
fs/nfs/idmap.c: In function 'nfs_idmap_request_key':
fs/nfs/idmap.c:170: error: implicit declaration of function 'IS_ERR_OR_NULL'
Caused by commit 892c16b2faae80ce1a3b3bd280a93533cd4f04a6 ("NFS: new
idmapper"). I guess an include of linux/err.h is missing.
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-09-30 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 3:58 Stephen Rothwell [this message]
2010-09-30 13:08 ` linux-next: build failure after merge of the final tree (nfs tree related) Bryan Schumaker
-- strict thread matches above, loose matches on Subject: below --
2013-11-18 2:20 Stephen Rothwell
2012-03-20 8:29 Stephen Rothwell
2012-03-20 13:25 ` Myklebust, Trond
2012-01-23 2:59 Stephen Rothwell
2012-01-23 18:10 ` Trond Myklebust
2012-01-24 8:38 ` Stanislav Kinsbursky
2010-08-04 4:54 Stephen Rothwell
2010-08-04 12:58 ` 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=20100930135834.dc73dfac.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=bjschuma@netapp$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=trond.myklebust@fys$(echo .)uio.no \
/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