From: Ralf Baechle <ralf@linux-mips.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Inotify: Fix build failure in inotify user support
Date: Fri, 30 Apr 2010 18:04:31 +0100 [thread overview]
Message-ID: <20100430170431.GA948@linux-mips.org> (raw)
In-Reply-To: <20100308195103.GA9228@linux-mips.org>
On Mon, Mar 08, 2010 at 08:51:03PM +0100, Ralf Baechle wrote:
> CONFIG_INOTIFY_USER defined but CONFIG_ANON_INODES undefined will result
> in the following build failure:
>
> LD vmlinux
> fs/built-in.o: In function 'sys_inotify_init1':
> (.text.sys_inotify_init1+0x22c): undefined reference to 'anon_inode_getfd'
> fs/built-in.o: In function `sys_inotify_init1':
> (.text.sys_inotify_init1+0x22c): relocation truncated to fit: R_MIPS_26 against 'anon_inode_getfd'
> make[2]: *** [vmlinux] Error 1
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
Ping. The problem still exists in rc6.
Ralf
next prev parent reply other threads:[~2010-04-30 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 19:51 [PATCH] Inotify: Fix build failure in inotify user support Ralf Baechle
2010-04-30 17:04 ` Ralf Baechle [this message]
2010-05-04 8:09 ` Florian Fainelli
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=20100430170431.GA948@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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