From: kbuild test robot <fengguang.wu@intel.com>
To: Will Woods <wwoods@redhat.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
kbuild-all@01.org
Subject: [mmotm:master 16/389] fs/notify/fanotify/fanotify_user.c:701:2: error: implicit declaration of function 'personality'
Date: Tue, 06 May 2014 10:30:05 +0800 [thread overview]
Message-ID: <5368492d.DPw+MmrkNUrQmF0Y%fengguang.wu@intel.com> (raw)
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: a51cc1787cdef3f17536d6a6dc1edd0e7a85988f
commit: efeebf123cce39e502749636d92de8f0a2b39b41 [16/389] fanotify: fix -EOVERFLOW with large files on 64-bit
config: make ARCH=ia64 allmodconfig
All error/warnings:
fs/notify/fanotify/fanotify_user.c: In function 'SYSC_fanotify_init':
>> fs/notify/fanotify/fanotify_user.c:701:2: error: implicit declaration of function 'personality' [-Werror=implicit-function-declaration]
>> fs/notify/fanotify/fanotify_user.c:701:1: error: 'PER_LINUX32' undeclared (first use in this function)
fs/notify/fanotify/fanotify_user.c:701:1: note: each undeclared identifier is reported only once for each function it appears in
cc1: some warnings being treated as errors
vim +/personality +701 fs/notify/fanotify/fanotify_user.c
695 if (unlikely(!oevent)) {
696 fd = -ENOMEM;
697 goto out_destroy_group;
698 }
699 group->overflow_event = &oevent->fse;
700
> 701 if (force_o_largefile())
702 event_f_flags |= O_LARGEFILE;
703 group->fanotify_data.f_flags = event_f_flags;
704 #ifdef CONFIG_FANOTIFY_ACCESS_PERMISSIONS
---
0-DAY kernel build testing backend Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild Intel Corporation
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2014-05-06 2:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5368492d.DPw+MmrkNUrQmF0Y%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=wwoods@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox