public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Paul Jackson <pj@sgi.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 09:15:00 +0200	[thread overview]
Message-ID: <4462E474.9020200@linux.intel.com> (raw)
In-Reply-To: <20060510233427.4306422b.pj@sgi.com>

Paul Jackson wrote:
> Arjan wrote:
>> This is patch one in a series of 17; to not overload lkml the other
>> 16 will be mailed direct; people who want to see them all can see
>> them at http://www.fenrus.org/unused
> 
> Well ... here's one case where your patch series is broken.
> 
> Argh - I almost missed this one.  My mailer is setup to tag all
> incoming lkml email that mentions the magic word 'cpuset'.  But
> it is not setup to catch indirect patches, needless to say.
> 
> One of your proposed changes (the only one I reviewed) removed the only
> EXPORT_SYMBOL_GPL in kernel/cpuset.c.  That EXPORT is needed because
> the routine in question is called from inlines which modules use.

not in the configs I tested at least... but maybe I need to add a specific config to
my set..

  reply	other threads:[~2006-05-11  7:16 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 [this message]
2006-05-11  8:06     ` Paul Jackson

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=4462E474.9020200@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    /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