From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 2 (rcutiny)
Date: Mon, 2 May 2011 15:34:35 -0700 [thread overview]
Message-ID: <20110502223435.GP2294@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110502083419.80cf9ad6.randy.dunlap@oracle.com>
On Mon, May 02, 2011 at 08:34:19AM -0700, Randy Dunlap wrote:
> On Mon, 2 May 2011 15:01:50 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110429:
>
>
> kernel/rcutiny_plugin.h:337: error: implicit declaration of function 'invoke_rcu_kthread'
> kernel/rcutiny.c:100: warning: conflicting types for 'invoke_rcu_kthread'
> kernel/rcutiny.c:100: error: static declaration of 'invoke_rcu_kthread' follows non-static declaration
> kernel/rcutiny_plugin.h:337: note: previous implicit declaration of 'invoke_rcu_kthread' was here
>
>
> randconfig is attached.
Ouch! Good catch. Fix applied to -rcu -- lost a declaration in the shuffle.
Thanx, Paul
next prev parent reply other threads:[~2011-05-02 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 5:01 linux-next: Tree for May 2 Stephen Rothwell
2011-05-02 15:19 ` linux-next: Tree for May 2 (uml builds fail) Randy Dunlap
2011-05-02 16:04 ` Michal Marek
2011-05-02 16:09 ` Randy Dunlap
2011-05-02 16:52 ` Sam Ravnborg
2011-05-02 20:33 ` Michal Marek
2011-05-02 15:34 ` linux-next: Tree for May 2 (rcutiny) Randy Dunlap
2011-05-02 22:34 ` Paul E. McKenney [this message]
2011-05-02 15:37 ` linux-next: Tree for May 2 (xen) Randy Dunlap
2011-05-02 16:15 ` linux-next: Tree for May 2 (uml irqs) Randy Dunlap
2011-05-02 16:34 ` Thomas Gleixner
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=20110502223435.GP2294@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=sfr@canb.auug.org.au \
/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).