From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] Fix modpost warnings by making start_secondary __cpuinit
Date: Fri, 1 Jun 2007 18:40:21 +0100 [thread overview]
Message-ID: <20070601174021.GA28461@linux-mips.org> (raw)
In-Reply-To: <20070602.013022.52128810.anemo@mba.ocn.ne.jp>
On Sat, Jun 02, 2007 at 01:30:22AM +0900, Atsushi Nemoto wrote:
> Looking at arch/mips/kernel/smp.c, I suppose there should be much more
> functions to be marked as __cpuinit. For example,
> prom_init_secondary(), prom_smp_finish(), prom_smp_finish(),
> prom_boot_secondary(), etc.
>
> And then, smtc_init_secondary(), smtc_smp_finish(), etc. ...
That is absolutely correct but beyond the minimal fix needed to deal with
the warning for 2.6.22. Longer term I'd like to get CPU hotplugging
working, it could be a handy feature with multi-threaded kernel models such
as VSMP and SMTC.
Ralf
prev parent reply other threads:[~2007-06-01 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S28573756AbXEaP7t/20070531155949Z+115@ftp.linux-mips.org>
2007-06-01 16:30 ` [MIPS] Fix modpost warnings by making start_secondary __cpuinit Atsushi Nemoto
2007-06-01 17:40 ` Ralf Baechle [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=20070601174021.GA28461@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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.