All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 1/6] powerpc: Move #ifdef'ed body of do_IRQ() into a separate function
Date: Thu, 30 Apr 2009 05:58:36 +1000	[thread overview]
Message-ID: <1241035116.16444.2.camel@pasglop> (raw)
In-Reply-To: <C9C597A9-3096-4BF1-8559-15FADFB2AEAD@kernel.crashing.org>

On Wed, 2009-04-29 at 07:48 -0500, Kumar Gala wrote:
> 
> I think Ben, Paul and I had discussed just universally enabling it.   
> Can't remember why Ben hadn't done that yet.

Slipped between the cracks. Patch welcome.

Cheers,
Ben.

  reply	other threads:[~2009-04-29 19:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  1:31 [PATCH 1/6] powerpc: Move #ifdef'ed body of do_IRQ() into a separate function Michael Ellerman
2009-04-23  1:31 ` [PATCH 2/6] powerpc: Move stack overflow check " Michael Ellerman
2009-04-23  1:31 ` [PATCH 3/6] powerpc: Move get_irq() comment into header Michael Ellerman
2009-04-23  1:31 ` [PATCH 4/6] powerpc: Remove fallback to __do_IRQ() Michael Ellerman
2009-04-23  1:31 ` [PATCH 5/6] powerpc/powermac: Use generic_handle_irq() in gatwick_action() Michael Ellerman
2009-04-23  1:31 ` [PATCH 6/6] powerpc: We don't need __do_IRQ() anymore Michael Ellerman
2009-04-23 16:49 ` [PATCH 1/6] powerpc: Move #ifdef'ed body of do_IRQ() into a separate function Scott Wood
2009-04-24  3:39   ` Michael Ellerman
2009-04-25 18:18 ` Christoph Hellwig
2009-04-28  0:49   ` Michael Ellerman
2009-04-29 11:44     ` Christoph Hellwig
2009-04-29 12:48       ` Kumar Gala
2009-04-29 19:58         ` Benjamin Herrenschmidt [this message]
2009-04-28 11:57 Michael Ellerman

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=1241035116.16444.2.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=galak@kernel.crashing.org \
    --cc=hch@lst.de \
    --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 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.