From: Paul Jackson <pj@sgi.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: akpm@osdl.org, bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/17] Infrastructure to mark exported symbols as unused-for-removal-soon
Date: Thu, 11 May 2006 01:06:58 -0700 [thread overview]
Message-ID: <20060511010658.c1e11d02.pj@sgi.com> (raw)
In-Reply-To: <4462E474.9020200@linux.intel.com>
Arjan wrote:
> not in the configs I tested at least... but maybe I need to add a specific config to
> my set..
Dang - I think you're right.
The original version of the patch that provided the new routine
cpuset_mem_spread_node() on about Feb 2, 2006 required that EXPORT, as
in that version cpuset_mem_spread_node() was called from the inline
versions of page_cache_alloc() and page_cache_alloc_cold().
But the final version of the cpuset_mem_spread_node() patch, on about
Feb 9, 2006, does not seem to require that EXPORT, because the callers
page_cache_alloc() and page_cache_alloc_code() were taken -out-of-line-
for the configurations that made use of cpuset_mem_spread_node().
However the EXPORT had already been added on about Feb 6 or 7, when
everyone and his brother noticed that I had broken the build with my
Feb 2 patch.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
prev parent reply other threads:[~2006-05-11 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 14:53 [patch 1/17] Infrastructure to mark exported symbols as unused-for-removal-soon Arjan van de Ven
2006-05-02 16:24 ` Randy.Dunlap
2006-05-02 16:23 ` Arjan van de Ven
2006-05-09 16:02 ` Andrew Morton
2006-05-09 16:13 ` Arjan van de Ven
2006-05-09 16:27 ` Jörn Engel
2006-05-09 17:23 ` Alan Cox
2006-05-11 6:34 ` Paul Jackson
2006-05-11 7:15 ` Arjan van de Ven
2006-05-11 8:06 ` Paul Jackson [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=20060511010658.c1e11d02.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.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 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.