From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Greg KH <gregkh@suse.de>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: Fw: Re: [kernel] Re: kernel/rcutree.h:301: sorry, unimplemented: inlining failed in call to 'rcu_bootup_announce': function body not available
Date: Fri, 18 Dec 2009 13:55:16 -0800 [thread overview]
Message-ID: <20091218215516.GG6712@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091218205456.GC6554@suse.de>
On Fri, Dec 18, 2009 at 12:54:56PM -0800, Greg KH wrote:
> On Fri, Dec 18, 2009 at 12:08:39PM -0800, Paul E. McKenney wrote:
> > Hello, Greg,
> >
> > Could you please consider the following commit for 2.6.32-stable?
> > It fixes a build error that some people are seeing.
> >
> > Thanx, Paul
> >
> > dbe01350fa8ce0c11948ab7d6be71a4d901be151 rcu: Remove inline from forward-referenced functions
>
> I'm guessing that you don't pay attention to the "now applied to the
> staging..." emails that I send out when I apply patches to different
> trees. This patch is already queued up for the 2.6.32.2 release which
> will happen in a few hours.
>
> {sigh}
Color me oblivious, and apologies for the noise!
Thanx, Paul
prev parent reply other threads:[~2009-12-18 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 20:08 Fw: Re: [kernel] Re: kernel/rcutree.h:301: sorry, unimplemented: inlining failed in call to 'rcu_bootup_announce': function body not available Paul E. McKenney
2009-12-18 20:54 ` Greg KH
2009-12-18 21:01 ` [stable] " Greg KH
2009-12-18 21:08 ` [kernel] " Mr. James W. Laferriere
2009-12-18 21:20 ` Greg KH
2009-12-18 21:55 ` Paul E. McKenney [this message]
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=20091218215516.GG6712@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@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