From: kbuild test robot <lkp@intel.com>
To: Paul Osmialowski <p.osmialowsk@samsung.com>
Cc: kbuild-all@01.org, Jonathan Corbet <corbet@lwn.net>,
Arnd Bergmann <arnd@arndb.de>,
Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Daniel Mack <daniel@zonque.org>,
Kay Sievers <kay.sievers@vrfy.org>, Joe Perches <joe@perches.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-api@vger.kernel.org,
Marcin Niesluchowski <m.niesluchow@samsung.com>,
Karol Lewandowski <k.lewandowsk@samsung.com>,
Paul Osmialowski <p.osmialowsk@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [RFC v3 1/9] printk: extract kmsg-related routines from printk.c to kmsg.c
Date: Mon, 19 Oct 2015 21:59:35 +0800 [thread overview]
Message-ID: <201510192124.Nt0hosFP%fengguang.wu@intel.com> (raw)
In-Reply-To: <1445259503-18158-2-git-send-email-p.osmialowsk@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 6304 bytes --]
Hi Paul,
[auto build test ERROR on next-20151016 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]
url: https://github.com/0day-ci/linux/commits/Paul-Osmialowski/Additional-kmsg-devices/20151019-211509
config: i386-defconfig (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All error/warnings (new ones prefixed by >>):
In file included from include/linux/fs.h:5:0,
from kernel/printk/kmsg.c:5:
kernel/printk/kmsg.c: In function 'devkmsg_read':
include/linux/wait.h:400:31: error: 'TASK_INTERRUPTIBLE' undeclared (first use in this function)
___wait_event(wq, condition, TASK_INTERRUPTIBLE, 0, 0, \
^
include/linux/wait.h:225:52: note: in definition of macro '___wait_event'
long __int = prepare_to_wait_event(&wq, &__wait, state);\
^
>> include/linux/wait.h:423:11: note: in expansion of macro '__wait_event_interruptible'
__ret = __wait_event_interruptible(wq, condition); \
^
>> kernel/printk/kmsg.c:105:9: note: in expansion of macro 'wait_event_interruptible'
ret = wait_event_interruptible(log_wait,
^
include/linux/wait.h:400:31: note: each undeclared identifier is reported only once for each function it appears in
___wait_event(wq, condition, TASK_INTERRUPTIBLE, 0, 0, \
^
include/linux/wait.h:225:52: note: in definition of macro '___wait_event'
long __int = prepare_to_wait_event(&wq, &__wait, state);\
^
>> include/linux/wait.h:423:11: note: in expansion of macro '__wait_event_interruptible'
__ret = __wait_event_interruptible(wq, condition); \
^
>> kernel/printk/kmsg.c:105:9: note: in expansion of macro 'wait_event_interruptible'
ret = wait_event_interruptible(log_wait,
^
include/linux/wait.h:198:43: error: 'TASK_KILLABLE' undeclared (first use in this function)
state == TASK_INTERRUPTIBLE || state == TASK_KILLABLE) \
^
include/linux/wait.h:230:7: note: in expansion of macro '___wait_is_interruptible'
if (___wait_is_interruptible(state) && __int) { \
^
include/linux/wait.h:400:2: note: in expansion of macro '___wait_event'
___wait_event(wq, condition, TASK_INTERRUPTIBLE, 0, 0, \
^
>> include/linux/wait.h:423:11: note: in expansion of macro '__wait_event_interruptible'
__ret = __wait_event_interruptible(wq, condition); \
^
>> kernel/printk/kmsg.c:105:9: note: in expansion of macro 'wait_event_interruptible'
ret = wait_event_interruptible(log_wait,
^
>> include/linux/wait.h:401:9: error: implicit declaration of function 'schedule' [-Werror=implicit-function-declaration]
schedule())
^
include/linux/wait.h:240:3: note: in definition of macro '___wait_event'
cmd; \
^
>> include/linux/wait.h:423:11: note: in expansion of macro '__wait_event_interruptible'
__ret = __wait_event_interruptible(wq, condition); \
^
>> kernel/printk/kmsg.c:105:9: note: in expansion of macro 'wait_event_interruptible'
ret = wait_event_interruptible(log_wait,
^
cc1: some warnings being treated as errors
vim +/schedule +401 include/linux/wait.h
82e06c81 Shaohua Li 2013-11-14 394 if (condition) \
82e06c81 Shaohua Li 2013-11-14 395 break; \
82e06c81 Shaohua Li 2013-11-14 396 __wait_event_cmd(wq, condition, cmd1, cmd2); \
82e06c81 Shaohua Li 2013-11-14 397 } while (0)
82e06c81 Shaohua Li 2013-11-14 398
35a2af94 Peter Zijlstra 2013-10-02 399 #define __wait_event_interruptible(wq, condition) \
35a2af94 Peter Zijlstra 2013-10-02 @400 ___wait_event(wq, condition, TASK_INTERRUPTIBLE, 0, 0, \
f13f4c41 Peter Zijlstra 2013-10-02 @401 schedule())
^1da177e Linus Torvalds 2005-04-16 402
^1da177e Linus Torvalds 2005-04-16 403 /**
^1da177e Linus Torvalds 2005-04-16 404 * wait_event_interruptible - sleep until a condition gets true
^1da177e Linus Torvalds 2005-04-16 405 * @wq: the waitqueue to wait on
^1da177e Linus Torvalds 2005-04-16 406 * @condition: a C expression for the event to wait for
^1da177e Linus Torvalds 2005-04-16 407 *
^1da177e Linus Torvalds 2005-04-16 408 * The process is put to sleep (TASK_INTERRUPTIBLE) until the
^1da177e Linus Torvalds 2005-04-16 409 * @condition evaluates to true or a signal is received.
^1da177e Linus Torvalds 2005-04-16 410 * The @condition is checked each time the waitqueue @wq is woken up.
^1da177e Linus Torvalds 2005-04-16 411 *
^1da177e Linus Torvalds 2005-04-16 412 * wake_up() has to be called after changing any variable that could
^1da177e Linus Torvalds 2005-04-16 413 * change the result of the wait condition.
^1da177e Linus Torvalds 2005-04-16 414 *
^1da177e Linus Torvalds 2005-04-16 415 * The function will return -ERESTARTSYS if it was interrupted by a
^1da177e Linus Torvalds 2005-04-16 416 * signal and 0 if @condition evaluated to true.
^1da177e Linus Torvalds 2005-04-16 417 */
^1da177e Linus Torvalds 2005-04-16 418 #define wait_event_interruptible(wq, condition) \
^1da177e Linus Torvalds 2005-04-16 419 ({ \
^1da177e Linus Torvalds 2005-04-16 420 int __ret = 0; \
e22b886a Peter Zijlstra 2014-09-24 421 might_sleep(); \
^1da177e Linus Torvalds 2005-04-16 422 if (!(condition)) \
35a2af94 Peter Zijlstra 2013-10-02 @423 __ret = __wait_event_interruptible(wq, condition); \
^1da177e Linus Torvalds 2005-04-16 424 __ret; \
^1da177e Linus Torvalds 2005-04-16 425 })
^1da177e Linus Torvalds 2005-04-16 426
:::::: The code at line 401 was first introduced by commit
:::::: f13f4c41c9cf9cd61c896e46e4e7ba2687e2af9c sched/wait: Collapse __wait_event_interruptible()
:::::: TO: Peter Zijlstra <peterz@infradead.org>
:::::: CC: Ingo Molnar <mingo@kernel.org>
---
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: 23978 bytes --]
next prev parent reply other threads:[~2015-10-19 14:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 12:58 [RFC v3 0/9] Additional kmsg devices Paul Osmialowski
2015-10-19 12:58 ` [RFC v3 1/9] printk: extract kmsg-related routines from printk.c to kmsg.c Paul Osmialowski
2015-10-19 13:53 ` kbuild test robot
2015-10-19 13:59 ` kbuild test robot [this message]
2015-10-19 12:58 ` [RFC v3 2/9] printk: add one function for storing log in proper format Paul Osmialowski
2015-10-19 12:58 ` [RFC v3 3/9] kmsg: introduce additional kmsg devices support Paul Osmialowski
2015-10-19 14:10 ` kbuild test robot
2015-10-19 12:58 ` [RFC v3 4/9] kmsg: add additional buffers support to memory class Paul Osmialowski
2015-10-19 13:54 ` kbuild test robot
2015-10-19 12:58 ` [RFC v3 5/9] kmsg: add function for adding and deleting additional buffers Paul Osmialowski
2015-10-19 18:20 ` kbuild test robot
2015-10-19 12:58 ` [RFC v3 6/9] kmsg: add ioctl for adding and deleting kmsg* devices Paul Osmialowski
2015-10-19 13:19 ` Arnd Bergmann
2015-10-19 12:58 ` [RFC v3 7/9] kmsg: add ioctl for kmsg* devices operating on buffers Paul Osmialowski
2015-10-19 12:58 ` [RFC v3 8/9] kmsg: add predefined _PID, _TID, _COMM keywords to kmsg* log dict Paul Osmialowski
2015-10-19 13:53 ` kbuild test robot
2015-10-19 14:11 ` kbuild test robot
2015-10-19 17:45 ` Andy Lutomirski
2015-10-20 11:16 ` Paul Osmialowski
2015-10-20 18:19 ` Andy Lutomirski
2015-10-19 12:58 ` [RFC v3 9/9] kmsg: selftests Paul Osmialowski
2015-10-22 0:32 ` Michael Ellerman
2015-10-19 13:26 ` [RFC v3 0/9] Additional kmsg devices Richard Weinberger
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=201510192124.Nt0hosFP%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=b.zolnierkie@samsung.com \
--cc=corbet@lwn.net \
--cc=daniel@zonque.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=k.lewandowsk@samsung.com \
--cc=kay.sievers@vrfy.org \
--cc=kbuild-all@01.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.niesluchow@samsung.com \
--cc=p.osmialowsk@samsung.com \
--cc=pmladek@suse.cz \
--cc=shuahkh@osg.samsung.com \
--cc=tj@kernel.org \
/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
all inboxes | Powered by JetHome®