From: kbuild test robot <lkp@intel.com>
To: "Pranay Kr. Srivastava" <pranjas@gmail.com>
Cc: kbuild-all@01.org, w.d.hubbs@gmail.com, chris@the-brannons.com,
kirk@reisers.ca, samuel.thibault@ens-lyon.org,
gregkh@linuxfoundation.org, sfr@canb.auug.org.au,
speakup@linux-speakup.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH-SPEAKUP 1/2] return same error value from spk_set_key_info
Date: Tue, 28 Feb 2017 20:13:22 +0800 [thread overview]
Message-ID: <201702281947.qmD9DVqC%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170222072027.4257-2-pranjas@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4363 bytes --]
Hi Pranay,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.10 next-20170228]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Pranay-Kr-Srivastava/return-same-error-value-from-spk_set_key_info/20170222-152440
config: i386-randconfig-c0-02281459 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All warnings (new ones prefixed by >>):
In file included from include/linux/linkage.h:4:0,
from include/linux/kernel.h:6,
from drivers/staging/speakup/main.c:21:
drivers/staging/speakup/main.c: In function 'spk_set_key_info':
>> include/linux/compiler.h:117:18: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'unsigned int' [-Wformat=]
static struct ftrace_branch_data \
^
include/linux/compiler.h:160:16: note: in definition of macro '__trace_if'
______r = !!(cond); \
^
include/linux/dynamic_debug.h:125:2: note: in expansion of macro 'if'
if (DYNAMIC_DEBUG_BRANCH(descriptor)) \
^
include/linux/compiler.h:139:58: note: in expansion of macro '__branch_check__'
# define unlikely(x) (__builtin_constant_p(x) ? !!(x) : __branch_check__(x, 0))
^
include/linux/dynamic_debug.h:117:2: note: in expansion of macro 'unlikely'
unlikely(descriptor.flags & _DPRINTK_FLAGS_PRINT)
^
include/linux/dynamic_debug.h:125:6: note: in expansion of macro 'DYNAMIC_DEBUG_BRANCH'
if (DYNAMIC_DEBUG_BRANCH(descriptor)) \
^
include/linux/printk.h:324:2: note: in expansion of macro 'dynamic_pr_debug'
dynamic_pr_debug(fmt, ##__VA_ARGS__)
^
drivers/staging/speakup/main.c:1228:3: note: in expansion of macro 'pr_debug'
pr_debug("too many key_infos (%d over %lu)\n",
^
vim +117 include/linux/compiler.h
2bcd521a Steven Rostedt 2008-11-21 101 };
2bcd521a Steven Rostedt 2008-11-21 102 };
2ed84eeb Steven Rostedt 2008-11-12 103
2ed84eeb Steven Rostedt 2008-11-12 104 /*
2ed84eeb Steven Rostedt 2008-11-12 105 * Note: DISABLE_BRANCH_PROFILING can be used by special lowlevel code
2ed84eeb Steven Rostedt 2008-11-12 106 * to disable branch tracing on a per file basis.
2ed84eeb Steven Rostedt 2008-11-12 107 */
d9ad8bc0 Bart Van Assche 2009-04-05 108 #if defined(CONFIG_TRACE_BRANCH_PROFILING) \
d9ad8bc0 Bart Van Assche 2009-04-05 109 && !defined(DISABLE_BRANCH_PROFILING) && !defined(__CHECKER__)
2ed84eeb Steven Rostedt 2008-11-12 110 void ftrace_likely_update(struct ftrace_branch_data *f, int val, int expect);
1f0d69a9 Steven Rostedt 2008-11-12 111
1f0d69a9 Steven Rostedt 2008-11-12 112 #define likely_notrace(x) __builtin_expect(!!(x), 1)
1f0d69a9 Steven Rostedt 2008-11-12 113 #define unlikely_notrace(x) __builtin_expect(!!(x), 0)
1f0d69a9 Steven Rostedt 2008-11-12 114
45b79749 Steven Rostedt 2008-11-21 115 #define __branch_check__(x, expect) ({ \
1f0d69a9 Steven Rostedt 2008-11-12 116 int ______r; \
2ed84eeb Steven Rostedt 2008-11-12 @117 static struct ftrace_branch_data \
1f0d69a9 Steven Rostedt 2008-11-12 118 __attribute__((__aligned__(4))) \
45b79749 Steven Rostedt 2008-11-21 119 __attribute__((section("_ftrace_annotated_branch"))) \
1f0d69a9 Steven Rostedt 2008-11-12 120 ______f = { \
1f0d69a9 Steven Rostedt 2008-11-12 121 .func = __func__, \
1f0d69a9 Steven Rostedt 2008-11-12 122 .file = __FILE__, \
1f0d69a9 Steven Rostedt 2008-11-12 123 .line = __LINE__, \
1f0d69a9 Steven Rostedt 2008-11-12 124 }; \
1f0d69a9 Steven Rostedt 2008-11-12 125 ______r = likely_notrace(x); \
:::::: The code at line 117 was first introduced by commit
:::::: 2ed84eeb8808cf3c9f039213ca137ffd7d753f0e trace: rename unlikely profiler to branch profiler
:::::: TO: Steven Rostedt <srostedt@redhat.com>
:::::: CC: Ingo Molnar <mingo@elte.hu>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27857 bytes --]
next prev parent reply other threads:[~2017-02-28 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 7:20 Pranay Kr. Srivastava
2017-02-22 7:20 ` [PATCH-SPEAKUP 1/2] return same error value from spk_set_key_info Pranay Kr. Srivastava
2017-02-22 10:26 ` Samuel Thibault
2017-02-24 15:32 ` kbuild test robot
2017-02-24 17:32 ` Greg KH
2017-02-28 12:13 ` kbuild test robot [this message]
2017-02-22 7:20 ` [PATCH-SPEAKUP 2/2] remove unecessary initial allocation of vc Pranay Kr. Srivastava
2017-02-22 10:27 ` Samuel Thibault
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=201702281947.qmD9DVqC%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kbuild-all@01.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=pranjas@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=sfr@canb.auug.org.au \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.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;
as well as URLs for NNTP newsgroup(s).