All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [rcu:rcu/next 5/78] kernel/rcutree.c:1131:41: error: 'flags' undeclared
Date: Thu, 20 Sep 2012 21:24:47 +0000	[thread overview]
Message-ID: <20120920212447.GB5446@localhost> (raw)

Hi Paul,

FYI, kernel build failed on

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
head:   d58ab773ab8bc98c81c7d49c04bc88b6e7968385
commit: 552116942862340a4a0577cbac194ddc6185e4cb [5/78] rcu: Move RCU grace-period cleanup into kthread
config: x86_64-allmodconfig

All related error/warning messages:

kernel/rcutree.c: In function 'rcu_gp_kthread':
kernel/rcutree.c:1131:41: error: 'flags' undeclared (first use in this function)
kernel/rcutree.c:1131:41: note: each undeclared identifier is reported only once for each function it appears in
kernel/rcutree.c:1131:74: warning: comparison of distinct pointer types lacks a cast [enabled by default]
kernel/rcutree.c:1176:74: warning: comparison of distinct pointer types lacks a cast [enabled by default]

vim +1131 kernel/rcutree.c
  1125				if (!ACCESS_ONCE(rnp->qsmask) &&
  1126				    !rcu_preempt_blocked_readers_cgp(rnp))
  1127					break;
  1128				flush_signals(current);
  1129			}
  1130	
> 1131			raw_spin_lock_irqsave(&rnp->lock, flags);
  1132			gp_duration = jiffies - rsp->gp_start;
  1133			if (gp_duration > rsp->gp_max)
  1134				rsp->gp_max = gp_duration;

---
0-DAY kernel build testing backend         Open Source Technology Centre
Fengguang Wu, Yuanhan Liu                              Intel Corporation

             reply	other threads:[~2012-09-20 21:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 21:24 Fengguang Wu [this message]
2012-09-20 21:58 ` [rcu:rcu/next 5/78] kernel/rcutree.c:1131:41: error: 'flags' undeclared Paul E. McKenney

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=20120920212447.GB5446@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.