From: kbuild test robot <lkp@intel.com>
To: Mike Rapoport <rapoport@il.ibm.com>
Cc: kbuild-all@01.org, Andrea Arcangeli <aarcange@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Mike Rapoport <mike.rapoport@gmail.com>
Subject: Re: [PATCH 3/5] uffd: Add fork() event
Date: Sun, 20 Mar 2016 20:53:28 +0800 [thread overview]
Message-ID: <201603202029.DGStOszG%fengguang.wu@intel.com> (raw)
In-Reply-To: <1458477741-6942-4-git-send-email-rapoport@il.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
Hi Pavel,
[auto build test ERROR on next-20160318]
[also build test ERROR on v4.5]
[cannot apply to v4.5-rc7 v4.5-rc6 v4.5-rc5]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Mike-Rapoport/userfaultfd-extension-for-non-cooperative-uffd-usage/20160320-204520
config: i386-tinyconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from kernel/fork.c:58:0:
include/linux/userfaultfd_k.h: In function 'dup_userfaultfd':
>> include/linux/userfaultfd_k.h:86:42: error: parameter name omitted
static inline int dup_userfaultfd(struct vm_area_struct *, struct list_head *)
^
include/linux/userfaultfd_k.h:86:67: error: parameter name omitted
static inline int dup_userfaultfd(struct vm_area_struct *, struct list_head *)
^
include/linux/userfaultfd_k.h: In function 'dup_userfaultfd_complete':
include/linux/userfaultfd_k.h:91:52: error: parameter name omitted
static inline void dup_userfaultfd_complete(struct list_head *)
^
vim +86 include/linux/userfaultfd_k.h
80
81 static inline bool userfaultfd_armed(struct vm_area_struct *vma)
82 {
83 return false;
84 }
85
> 86 static inline int dup_userfaultfd(struct vm_area_struct *, struct list_head *)
87 {
88 return 0;
89 }
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6262 bytes --]
next prev parent reply other threads:[~2016-03-20 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 12:42 [PATCH 0/5] userfaultfd: extension for non cooperative uffd usage Mike Rapoport
2016-03-20 12:42 ` [PATCH 1/5] uffd: Split the find_userfault() routine Mike Rapoport
2016-03-20 12:42 ` [PATCH 2/5] uffd: Add ability to report non-PF events from uffd descriptor Mike Rapoport
2016-03-20 12:42 ` [PATCH 3/5] uffd: Add fork() event Mike Rapoport
2016-03-20 12:53 ` kbuild test robot [this message]
2016-03-20 12:42 ` [PATCH 4/5] uffd: Add mremap() event Mike Rapoport
2016-03-20 12:42 ` [PATCH 5/5] uffd: Add madvise() event for MADV_DONTNEED request Mike Rapoport
2016-03-21 9:54 ` [PATCH 0/5] userfaultfd: extension for non cooperative uffd usage Pavel Emelyanov
2016-04-06 6:14 ` Mike Rapoport
2016-04-20 9:44 ` Pavel Emelyanov
2016-04-22 16:05 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2015-05-13 14:52 [PATCH 0/5] UserfaultFD: Extension for non cooperative uffd usage (v2) Pavel Emelyanov
2015-05-13 14:54 ` [PATCH 3/5] uffd: Add fork() event Pavel Emelyanov
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=201603202029.DGStOszG%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=aarcange@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.rapoport@gmail.com \
--cc=rapoport@il.ibm.com \
--cc=xemul@parallels.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