From: Adrian Bunk <bunk@kernel.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jan Dittmer <jdi@l4x.org>,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-alpha@vger.kernel.org
Subject: Re: [1/4] 2.6.23-rc4: known regressions
Date: Fri, 31 Aug 2007 10:03:51 +0200 [thread overview]
Message-ID: <20070831080351.GD9260@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0708310043250.14694@schroedinger.engr.sgi.com>
On Fri, Aug 31, 2007 at 12:48:45AM -0700, Christoph Lameter wrote:
> Here is the fix for alpha:
>
> >From clameter@sgi.com Thu Aug 30 14:13:57 2007
> Subject: SLUB: Force inlining for functions in slub_def.h
>
> Some compilers (especially older gcc releases) may skip inlining sometimes
> which will lead to link failures. Force the inlining of keyfunctions in
> slub_def.h to avoid these issues.
>...
This also explains why it's an Alpha-only problem - the Alpha port
pretty much diverges from the rest of the kernel regarding "inline"
semantics and usage...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-08-31 8:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 15:26 [1/4] 2.6.23-rc4: known regressions Michal Piotrowski
2007-08-29 18:04 ` Jan Dittmer
2007-08-29 23:29 ` [2.6.23 patch] xtensa process.c must #include <linux/fs.h> Adrian Bunk
2007-08-29 23:47 ` [1/4] 2.6.23-rc4: known regressions Adrian Bunk
2007-08-30 0:11 ` Christoph Lameter
2007-08-30 0:39 ` Christoph Lameter
2007-08-30 7:10 ` Jan Dittmer
2007-08-30 18:12 ` Christoph Lameter
2007-08-30 18:46 ` Jan Dittmer
2007-08-31 7:48 ` Christoph Lameter
2007-08-31 7:48 ` Christoph Lameter
2007-08-31 8:03 ` Adrian Bunk [this message]
2007-08-29 19:07 ` Jeff Chua
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=20070831080351.GD9260@stusta.de \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=jdi@l4x.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=torvalds@linux-foundation.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.