From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: powerpc/mpic: Fix allocation of reverse-map for multi-ISU mpics
Date: Thu, 23 Feb 2012 12:55:08 +1100 [thread overview]
Message-ID: <1329962108.20389.19.camel@pasglop> (raw)
In-Reply-To: <20120223013947.GC3212@ponder.secretlab.ca>
On Wed, 2012-02-22 at 18:39 -0700, Grant Likely wrote:
>
> Looks fine to me. This will conflict with the irqdomain tree in linux-next,
> but it will be a trivial fixup. Still, if you prefer I can pick this
> up into my tree.
Well, I'm also going to carry a slightly modified variant of Kyle's
mpic series so we'll have to deal with conflicts regardless, I'll
keep that one.
What I might do tho is pull your tree in powerpc-next at some point,
when you tell me it's frozen solid, this will potentially make my life
easier.
Cheers,
Ben.
next prev parent reply other threads:[~2012-02-23 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 23:50 powerpc/mpic: Fix allocation of reverse-map for multi-ISU mpics Benjamin Herrenschmidt
2012-02-23 1:39 ` Grant Likely
2012-02-23 1:55 ` Benjamin Herrenschmidt [this message]
2012-02-23 1:59 ` Grant Likely
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=1329962108.20389.19.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@lists.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.