From: Michael Ellerman <michael@ellerman•id.au>
To: Christoph Hellwig <hch@lst•de>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: [PATCH 1/6] powerpc: Move #ifdef'ed body of do_IRQ() into a separate function
Date: Tue, 28 Apr 2009 10:49:07 +1000 [thread overview]
Message-ID: <1240879747.11027.2.camel@localhost> (raw)
In-Reply-To: <20090425181823.GA10481@lst.de>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
On Sat, 2009-04-25 at 20:18 +0200, Christoph Hellwig wrote:
> On Thu, Apr 23, 2009 at 11:31:37AM +1000, Michael Ellerman wrote:
> > +#ifdef CONFIG_IRQSTACKS
>
> Wasn't there a plan to make CONFIG_IRQSTACKS the unconditional default?
Not sure. Looks like the 64-bit configs all turn it on, and all but one
or two of the 32-bit configs don't.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-28 0:49 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 [this message]
2009-04-29 11:44 ` Christoph Hellwig
2009-04-29 12:48 ` Kumar Gala
2009-04-29 19:58 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
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=1240879747.11027.2.camel@localhost \
--to=michael@ellerman$(echo .)id.au \
--cc=hch@lst$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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