From: divya <dipraksh@linux.vnet.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, sripathik@in.ibm.com
Subject: kernel version 2.6.35-git10 build failure
Date: Wed, 11 Aug 2010 12:51:35 +0530 [thread overview]
Message-ID: <4C624F7F.3070608@linux.vnet.ibm.com> (raw)
Hi,
Today kernel(version 2.6.35-git10 -commitid 3d30701b58970) build fails with following error on both system x and p
fs/9p/vfs_inode.c: In function 'v9fs_vfs_setattr_dotl':
fs/9p/vfs_inode.c:1267: error: implicit declaration of function 'inode_setattr'
make[2]: *** [fs/9p/vfs_inode.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [fs/9p] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [fs] Error 2
make: *** Waiting for unfinished jobs....
Seems like the commit 87d7845aa0b is the corrupt which added the function v9fs_vfs_setattr_dotl()
Thanks
Divya
next reply other threads:[~2010-08-11 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 7:21 divya [this message]
2010-08-11 7:51 ` kernel version 2.6.35-git10 build failure Stephen Rothwell
2010-08-11 7:51 ` Stephen Rothwell
2010-08-11 7:53 ` Sripathi Kodi
2010-08-11 7:53 ` Sripathi Kodi
2010-08-11 8:59 ` Piotr Hosowicz
2010-08-11 8:59 ` Piotr Hosowicz
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=4C624F7F.3070608@linux.vnet.ibm.com \
--to=dipraksh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sripathik@in.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.