linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Kevin Corry <kevcorry@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Carl Love <carll@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	Stephane Eranian <eranian@hpl.hp.com>
Subject: Re: [PATCH 2/2] powerpc: change topology_init() to a subsys_initcall
Date: Thu, 03 May 2007 11:11:47 +1000	[thread overview]
Message-ID: <1178154707.5338.11.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <200705021211.49331.kevcorry@us.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]

On Wed, 2007-05-02 at 12:11 -0500, Kevin Corry wrote:
> Change the powerpc version of topology_init() from an __initcall to
> a subsys_initcall to match all other architectures.
> 
> Signed-off-by: Kevin Corry <kevcorry@us.ibm.com>
> 
> Index: linux-2.6.21/arch/powerpc/kernel/sysfs.c
> ===================================================================
> --- linux-2.6.21.orig/arch/powerpc/kernel/sysfs.c
> +++ linux-2.6.21/arch/powerpc/kernel/sysfs.c
> @@ -498,4 +498,4 @@ static int __init topology_init(void)
>  
>  	return 0;
>  }
> -__initcall(topology_init);
> +subsys_initcall(topology_init);      

topology_init() depends on the register_one_node() stuff being
available, which relies on register_node_type() being called AFAICT -
which is a postcore_initcall(). So that's OK.

It also creates sysfs files, which is OK because long before initcalls
run vfs_caches_init() called mnt_init() which called sysfs_init().

Just to be super safe it'd be good to diff your sysfs before and after
the change. But assuming that show's nothing this looks fine to me.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-03  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 17:08 [PATCH 0/2] powerpc: perfmon2 prereqs Kevin Corry
2007-05-02 17:10 ` [PATCH 1/2] powerpc: add smp_call_function_single() Kevin Corry
2007-05-02 17:11 ` [PATCH 2/2] powerpc: change topology_init() to a subsys_initcall Kevin Corry
2007-05-03  1:11   ` Michael Ellerman [this message]
2007-05-03 13:26     ` Kevin Corry

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=1178154707.5338.11.camel@concordia.ozlabs.ibm.com \
    --to=michael@ellerman.id.au \
    --cc=carll@us.ibm.com \
    --cc=eranian@hpl.hp.com \
    --cc=kevcorry@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).