From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [103.22.144.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 6C5781A019A for ; Fri, 13 Mar 2015 10:34:32 +1100 (AEDT) Message-ID: <1426203271.2772.3.camel@ellerman.id.au> Subject: Re: [PATCH 0/8] powerpc/8xx: Getting rid of CONFIG_8xx From: Michael Ellerman To: Christophe Leroy Date: Fri, 13 Mar 2015 10:34:31 +1100 In-Reply-To: <20150312152420.11C821A2425@localhost.localdomain> References: <20150312152420.11C821A2425@localhost.localdomain> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: Paul Mackerras , linuxppc-dev list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2015-03-12 at 16:24 +0100, Christophe Leroy wrote: > Two config options exist to define powerpc MPC8xx: > * CONFIG_PPC_8xx > * CONFIG_8xx > In addition, CONFIG_PPC_8xx also defines CONFIG_CPM1 as > communication co-processor > > arch/powerpc/platforms/Kconfig.cputype has contained the following > comment about CONFIG_8xx item for some years: > "# this is temp to handle compat with arch=ppc" > > It looks like not many places still have that old CONFIG_8xx used, > so it is likely to be a good time to get rid of it completely ? > > Patchset is composed of the following patches: > [1/8] powerpc: replace CONFIG_8xx by CONFIG_PPC_8xx > [2/8] um: replace CONFIG_8xx by CONFIG_PPC_8xx > [3/8] video: replace CONFIG_8xx by CONFIG_PPC_8xx > [4/8] net: freescale: replace CONFIG_8xx by CONFIG_PPC_8xx > [5/8] tty: cpm_uart: replace CONFIG_8xx by CONFIG_CPM1 > [6/8] mtd: replace CONFIG_8xx by CONFIG_PPC_8xx > [7/8] isdn: replace CONFIG_8xx by CONFIG_PPC_8xx > [8/8] powerpc: get rid of CONFIG_8xx > > All but the last one are independant and can be applied in any > order. Only the 8th one requires the first 7 patches to be applied. Sounds good. I only see 0, 4 and 7 on linuxppc-dev for some reason. You'll need to collect ACKs, or get the individual patches merged, and then we can take patch 8 through the powerpc tree once those are all in - probably for 4.2. cheers