From: kbuild test robot <lkp@intel.com>
To: Dave Watson <davejwatson@fb.com>
Cc: kbuild-all@01.org, davejwatson@fb.com, kernel-team@fb.com,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
pjt@google.com, mathieu.desnoyers@efficios.com
Subject: Re: [RFC PATCH 1/3] restartable sequences: user-space per-cpu critical sections
Date: Fri, 23 Oct 2015 02:53:41 +0800 [thread overview]
Message-ID: <201510230203.337YMkHy%fengguang.wu@intel.com> (raw)
In-Reply-To: <581c0b6403285219724961a3d250c6d95dfacea7.1445464158.git.davejwatson@fb.com>
Hi Dave,
[auto build test WARNING on v4.3-rc6 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Dave-Watson/restartable-sequences-benchmarks/20151023-020939
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
include/linux/radix-tree.h:212:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
--
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
--
mm/page_alloc.c:6010:1: sparse: directive in argument list
mm/page_alloc.c:6012:1: sparse: directive in argument list
mm/page_alloc.c:6019:1: sparse: directive in argument list
mm/page_alloc.c:6021:1: sparse: directive in argument list
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
--
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
include/linux/radix-tree.h:212:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:196:16: sparse: incompatible types in comparison expression (different address spaces)
--
mm/debug.c:176:1: sparse: directive in argument list
mm/debug.c:178:1: sparse: directive in argument list
mm/debug.c:187:1: sparse: directive in argument list
mm/debug.c:189:1: sparse: directive in argument list
mm/debug.c:190:1: sparse: directive in argument list
mm/debug.c:192:1: sparse: directive in argument list
mm/debug.c:194:1: sparse: directive in argument list
mm/debug.c:196:1: sparse: directive in argument list
mm/debug.c:197:1: sparse: directive in argument list
mm/debug.c:199:1: sparse: directive in argument list
mm/debug.c:200:1: sparse: directive in argument list
mm/debug.c:202:1: sparse: directive in argument list
mm/debug.c:206:1: sparse: directive in argument list
mm/debug.c:208:1: sparse: directive in argument list
mm/debug.c:221:1: sparse: directive in argument list
mm/debug.c:223:1: sparse: directive in argument list
mm/debug.c:224:1: sparse: directive in argument list
mm/debug.c:226:1: sparse: directive in argument list
mm/debug.c:228:1: sparse: directive in argument list
mm/debug.c:230:1: sparse: directive in argument list
mm/debug.c:231:1: sparse: directive in argument list
mm/debug.c:233:1: sparse: directive in argument list
mm/debug.c:234:1: sparse: directive in argument list
mm/debug.c:236:1: sparse: directive in argument list
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
--
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
include/linux/radix-tree.h:212:16: sparse: incompatible types in comparison expression (different address spaces)
include/linux/radix-tree.h:212:16: sparse: incompatible types in comparison expression (different address spaces)
--
include/linux/sched.h:1189:34: sparse: Expected ) in function declarator
include/linux/sched.h:1189:34: sparse: got (
>> builtin:0:0: sparse: expected ; at end of declaration
include/linux/sched.h:1190:1: sparse: Expected ; at the end of type declaration
include/linux/sched.h:1190:1: sparse: got }
mm/memcontrol.c:3289:21: sparse: incompatible types in comparison expression (different address spaces)
mm/memcontrol.c:3291:21: sparse: incompatible types in comparison expression (different address spaces)
mm/memcontrol.c:4861:23: sparse: incompatible types in comparison expression (different address spaces)
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2015-10-22 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:06 [RFC PATCH 0/3] restartable sequences benchmarks Dave Watson
2015-10-22 18:06 ` [RFC PATCH 1/3] restartable sequences: user-space per-cpu critical sections Dave Watson
2015-10-22 18:53 ` kbuild test robot [this message]
2015-10-22 19:35 ` kbuild test robot
2015-10-22 18:06 ` [RFC PATCH 2/3] restartable sequences: x86 ABI Dave Watson
2015-10-22 18:07 ` [RFC PATCH 3/3] restartable sequences: basic user-space self-tests Dave Watson
2015-10-22 19:11 ` [RFC PATCH 0/3] restartable sequences benchmarks Andy Lutomirski
2015-10-22 22:10 ` Dave Watson
-- strict thread matches above, loose matches on Subject: below --
2015-06-24 22:26 [RFC PATCH 0/3] restartable sequences: fast user-space percpu critical sections Paul Turner
2015-06-24 22:26 ` [RFC PATCH 1/3] restartable sequences: user-space per-cpu " Paul Turner
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=201510230203.337YMkHy%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davejwatson@fb.com \
--cc=kbuild-all@01.org \
--cc=kernel-team@fb.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=pjt@google.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
Powered by JetHome