From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
"Luck, Tony" <tony.luck@intel.com>, Andi Kleen <ak@suse.de>,
Michael Ellerman <michaele@au.ibm.com>
Subject: Re: [PATCH 0/5] Message signaled irq handling cleanups
Date: Thu, 28 Sep 2006 08:51:07 +1000 [thread overview]
Message-ID: <1159397467.18293.85.camel@localhost.localdomain> (raw)
In-Reply-To: <1159396605.18293.83.camel@localhost.localdomain>
> At this point, best is that we finish a working implementation based on
> Michael reworked core for PowerPC (which is currently located in
> arch/powerpc and doesn't exclude whatever sits in drivers/pci/ except
> that we don't build the later on PowerPC) so you can see more what our
> approach looks like and why we need to go that way.
Don't look for it in the tree btw, it's not beem merged, though Michael
posted some versions to linuxppc-dev.
Ben.
next prev parent reply other threads:[~2006-09-27 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 19:55 [PATCH 0/5] Message signaled irq handling cleanups Eric W. Biederman
2006-09-27 19:58 ` [PATCH 1/5] msi: Simplify msi sanity checks by adding with generic irq code Eric W. Biederman
2006-09-27 19:58 ` [PATCH 2/5] msi: Only use a single irq_chip for msi interrupts Eric W. Biederman
2006-09-27 19:58 ` [PATCH 3/5] msi: Refactor and move the msi irq_chip into the arch code Eric W. Biederman
2006-09-27 19:58 ` [PATCH 4/5] msi: Move the ia64 code into arch/ia64 Eric W. Biederman
2006-09-27 19:58 ` [PATCH 5/5] htirq: Tidy up the htirq code Eric W. Biederman
2006-09-27 20:29 ` [PATCH 0/5] Message signaled irq handling cleanups Eric W. Biederman
2006-09-27 22:36 ` Benjamin Herrenschmidt
2006-09-27 22:51 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-27 19:54 Eric W. Biederman
2006-09-27 19:54 Eric W. Biederman
2006-09-27 22:57 ` Andi Kleen
2006-09-28 4:02 ` Eric W. Biederman
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=1159397467.18293.85.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michaele@au.ibm.com \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.com \
/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