From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [203.10.76.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx.ozlabs.org", Issuer "CA Cert Signing Authority" (verified OK)) by bilbo.ozlabs.org (Postfix) with ESMTPS id 0EC20B727C for ; Fri, 19 Jun 2009 18:30:31 +1000 (EST) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by ozlabs.org (Postfix) with SMTP id CBACEDDD1B for ; Fri, 19 Jun 2009 18:30:28 +1000 (EST) Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 19 Jun 2009 10:30:24 +0200 From: "Gerhard Pircher" In-Reply-To: Message-ID: <20090619083024.309900@gmx.net> MIME-Version: 1.0 References: Subject: Re: killing use of ppc_md.init To: Kumar Gala , benh@kernel.crashing.org Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , -------- Original-Nachricht -------- > Datum: Thu, 18 Jun 2009 09:38:50 -0500 > Von: Kumar Gala > An: Gerhard Pircher , Benjamin Herrenschmidt > CC: linuxppc-dev list > Betreff: killing use of ppc_md.init > ppc_md.init only exists on ppc32 and seems like its pretty useless > today. The users seem to fall into two classes: > > 1. called to do of_platform_bus_probe() - most platforms use > machine_device_initcall() for this > 2. some platform init code which seems like it could move into > setup_arch(). > > The second one seems to only be on amigaone and chrp. Anyone know if > there is any harm in moving the amigaone_init() into > amigaone_setup_arch() and similarly on chrp chrp_init2() into > chrp_setup_arch(). I guess converting amigaone_init() to a machine_device_initcall() is the easiest approach. I'll send a patch soon. Gerhard -- GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate und Telefonanschluss für nur 17,95 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02