All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [vfs:for-next 54/99] kernel/signal.c:1974:6: error: wrong type argument to unary exclamation mark
Date: Sat, 28 Jul 2012 10:33:48 +0000	[thread overview]
Message-ID: <20120728103348.GC10759@localhost> (raw)

Hi Al,

This kernel build error stop at commit 158e1645e ("trim task_work: get rid of
hlist"), when ->task_works is changed to a pointer:

-       struct hlist_head task_works;
+       void *task_works;

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-next
head:   8cae6f7158ec1fa44c8a04a43db7d8020ec60437
commit: 7266702805f9d824f92ce5c4069eca65d0f21d28 [54/99] signal: make sure we don't get stopped with pending task_work

All related error/warning messages:

kernel/signal.c: In function 'ptrace_notify':
kernel/signal.c:1974:6: error: wrong type argument to unary exclamation mark
kernel/signal.c: In function 'get_signal_to_deliver':
kernel/signal.c:2201:6: error: wrong type argument to unary exclamation mark

vim +1974 kernel/signal.c
  1971	void ptrace_notify(int exit_code)
  1972	{
  1973		BUG_ON((exit_code & (0x7f | ~0xffff)) != SIGTRAP);
> 1974		if (unlikely(current->task_works)) {
  1975			if (test_and_clear_ti_thread_flag(current_thread_info(),
  1976							   TIF_NOTIFY_RESUME)) {
  1977				smp_mb__after_clear_bit();

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com>                     Intel Corporation

                 reply	other threads:[~2012-07-28 10:33 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=20120728103348.GC10759@localhost \
    --to=fengguang.wu@intel.com \
    --cc=kernel-janitors@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.