From: Greg KH <gregkh@suse.de>
To: "Mr. James W. Laferriere" <babydr@baby-dragons.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
stable@kernel.org, linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [kernel] 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:20:48 -0800 [thread overview]
Message-ID: <20091218212048.GA17834@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.01.0912181202320.9874@filesrv1.baby-dragons.com>
On Fri, Dec 18, 2009 at 12:08:12PM -0900, Mr. James W. Laferriere wrote:
> Fyi , There is another driver that has this issue as well ,
> fusion/mptsas , has a 'inline' in drivers/message/fusion/mptsas.c at line
> 105 that causes compile time failure in the same vein .
> See email to linux-scsi , Subject: linux-2.6.32.1 drivers/message/fusion/mptsas.c:106: sorry, unimplemented: inlining failed in call to 'mptsas_set_rphy': function body not available
Is there a patch in Linus's tree that solves this problem already? If
so, what is the git commit id of it?
> I am also having 'ld' time troubles with
> drivers/gpu/drm/radeon/radeon_test.c:45: undefined reference to `__udivdi3' and
> have sent emails to the appropriate lists & maintainers(I hope) .
When that gets fixed, let the stable@kernel.org address know the git
commit id that needs to be applied.
> Don't know if any of these would/should hold up the push of 32.2 or not
Don't worry, it will not :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-12-18 21:21 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 [this message]
2009-12-18 21:55 ` 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=20091218212048.GA17834@suse.de \
--to=gregkh@suse.de \
--cc=babydr@baby-dragons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--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