From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [RFC/PATCH 4/4] Simplify xics direct/lpar irq_host setup
Date: Fri, 18 Apr 2008 14:16:31 +1000 [thread overview]
Message-ID: <1208492191.6958.392.camel@pasglop> (raw)
In-Reply-To: <e16ca5457060787c0d339e1b707e75c6f875f7b6.1207032121.git.michael@ellerman.id.au>
On Tue, 2008-04-01 at 17:42 +1100, Michael Ellerman wrote:
> The xics code currently has a direct and lpar variant of xics_host_map, the
> only difference being which irq_chip they use. If we remember which irq_chip
> we're using we can combine these two routines. That also allows us to have a
> single irq_host_ops instead of two.
>
> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
> ---
Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2008-04-18 4:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 6:42 [RFC/PATCH 1/4] Move xics_setup_8259_cascade() into platforms/pseries/setup.c Michael Ellerman
2008-04-01 6:42 ` [RFC/PATCH 2/4] Turn xics_setup_8259_cascade() into a generic pseries_setup_i8259_cascade() Michael Ellerman
2008-04-18 4:05 ` Benjamin Herrenschmidt
2008-04-01 6:42 ` [RFC/PATCH 3/4] Use pseries_setup_i8259_cascade() in pseries_mpic_init_IRQ() Michael Ellerman
2008-04-18 4:15 ` Benjamin Herrenschmidt
2008-04-18 4:47 ` Michael Ellerman
2008-04-01 6:42 ` [RFC/PATCH 4/4] Simplify xics direct/lpar irq_host setup Michael Ellerman
2008-04-18 4:16 ` Benjamin Herrenschmidt [this message]
2008-04-18 3:59 ` [RFC/PATCH 1/4] Move xics_setup_8259_cascade() into platforms/pseries/setup.c Benjamin Herrenschmidt
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=1208492191.6958.392.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).