public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: linux-kernel@vger.kernel.org, ak@muc.de, matthew.e.tolentino@intel.com
Subject: Re: __cpuinit functions wrongly marked __meminit
Date: Fri, 20 Jan 2006 18:00:15 -0800	[thread overview]
Message-ID: <20060120180015.061686fd.akpm@osdl.org> (raw)
In-Reply-To: <20060120173723.A7060@unix-os.sc.intel.com>

Ashok Raj <ashok.raj@intel.com> wrote:
>
> __meminit has overzelously been modified and crept its way
> into marking cpuup callbacks as __meminit. 

OK.

We do have tools which will auto-detect things like this. 
reference_discarded.pl, reference_init.pl.  I think they should work in
this case.  One would need to use a number of .config combinations to get
full coverage of course.  

  reply	other threads:[~2006-01-21  1:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21  1:37 __cpuinit functions wrongly marked __meminit Ashok Raj
2006-01-21  2:00 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-21 16:45 Tolentino, Matthew E

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=20060120180015.061686fd.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@muc.de \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.e.tolentino@intel.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