linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 01/10] powerpc: Remove use of CONFIG_PPC_MERGE
Date: Sat, 02 Aug 2008 12:38:55 +1000	[thread overview]
Message-ID: <1217644735.7471.21.camel@localhost> (raw)
In-Reply-To: <1217609060-6381-2-git-send-email-galak@kernel.crashing.org>

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

On Fri, 2008-08-01 at 11:44 -0500, Kumar Gala wrote:
> Now that arch/ppc is gone we don't need CONFIG_PPC_MERGE anymore remove
> the dead code associated with !CONFIG_PPC_MERGE out of arch/powerpc
> and include/asm-powerpc.
...

> diff --git a/include/asm-powerpc/irq.h b/include/asm-powerpc/irq.h
> index 1ef8e30..a372f76 100644
> --- a/include/asm-powerpc/irq.h
> +++ b/include/asm-powerpc/irq.h
...
> -#define	SIU_INT_PC4		((uint)0x3b + CPM_IRQ_OFFSET)
> -#define	SIU_INT_PC3		((uint)0x3c + CPM_IRQ_OFFSET)
> -#define	SIU_INT_PC2		((uint)0x3d + CPM_IRQ_OFFSET)
> -#define	SIU_INT_PC1		((uint)0x3e + CPM_IRQ_OFFSET)
> -#define	SIU_INT_PC0		((uint)0x3f + CPM_IRQ_OFFSET)
> -
> -#endif /* CONFIG_8260 */
> -
> -#endif /* Whatever way too big #ifdef */

I'll miss that one, it made me laugh once.

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 --]

  parent reply	other threads:[~2008-08-02  2:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 16:44 [PATCH 00/10] powerpc: Remove use of CONFIG_PPC_MERGE Kumar Gala
2008-08-01 16:44 ` [PATCH 01/10] " Kumar Gala
2008-08-01 16:44   ` [PATCH 02/10] usb: remove code associated with !CONFIG_PPC_MERGE Kumar Gala
2008-08-01 16:44     ` [PATCH 03/10] fs-enet: " Kumar Gala
2008-08-01 16:44       ` [PATCH 04/10] netdev: drop CONFIG_PPC_MERGE from Kconfig Kumar Gala
2008-08-01 16:44         ` [PATCH 05/10] rtc: use CONFIG_PPC instead of CONFIG_PPC_MERGE Kumar Gala
2008-08-01 16:44           ` [PATCH 06/10] serial/mpc52xx_uart: remove code associated with !CONFIG_PPC_MERGE Kumar Gala
2008-08-01 16:44             ` [PATCH 07/10] mpc52xx_psc_spi: " Kumar Gala
2008-08-01 16:44               ` [PATCH 08/10] powerpc: convert CONFIG_PPC_MERGE to CONFIG_PPC for legacy io checks Kumar Gala
2008-08-01 16:44                 ` [PATCH 09/10] pata_sil680: convert CONFIG_PPC_MERGE to CONFIG_PPC Kumar Gala
2008-08-01 16:44                   ` [PATCH 10/10] mtd: remove code associated with !CONFIG_PPC_MERGE Kumar Gala
2008-08-01 17:49                     ` Josh Boyer
2008-08-01 18:57       ` [PATCH 03/10] fs-enet: " Scott Wood
2008-08-02  2:38   ` Michael Ellerman [this message]
2008-08-01 23:53 ` [PATCH 00/10] powerpc: Remove use of CONFIG_PPC_MERGE Paul Mackerras

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=1217644735.7471.21.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=galak@kernel.crashing.org \
    --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).