From: Christoph Lameter <clameter@sgi.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init
Date: Tue, 10 Jul 2007 12:43:39 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707101243240.12485@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070710190123.GB3492@stusta.de>
On Tue, 10 Jul 2007, Adrian Bunk wrote:
> But I'm not convinced it's really worth manually forcing noinline only
> for moving a few bytes to __init in the CONFIG_NUMA=y case - in the
> long term this will only bit rot.
Allright then
Acked-by: Christoph Lameter <clameter@sgi.com>
prev parent reply other threads:[~2007-07-10 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 12:44 Adrian Bunk
2007-07-10 18:33 ` Christoph Lameter
2007-07-10 19:01 ` Adrian Bunk
2007-07-10 19:43 ` Christoph Lameter [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=Pine.LNX.4.64.0707101243240.12485@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®