From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: Meador Inge <meador_inge@mentor.com>,
openmcapi-dev@googlegroups.com,
devicetree-discuss@lists.ozlabs.org,
Hollis Blanchard <hollis_blanchard@mentor.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] powerpc: add support for MPIC message register API
Date: Sat, 18 Jun 2011 08:58:53 +1000 [thread overview]
Message-ID: <1308351533.32158.61.camel@pasglop> (raw)
In-Reply-To: <20110617115828.3cebd5c9@schlenkerla.am.freescale.net>
On Fri, 2011-06-17 at 11:58 -0500, Scott Wood wrote:
> When did this change from "considered an internal implementation
> issue, and not really an interface" to "all new interfaces"?
Interesting blurb... that's not everybody's opinion and I would argue
that supporting AMP kernels isn't something we want to do with closed
source crap.
Ben.
next prev parent reply other threads:[~2011-06-17 22:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 19:19 [PATCH v3 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-05-31 19:19 ` Meador Inge
2011-05-31 19:19 ` [PATCH v3 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-05-31 19:23 ` Scott Wood
2011-06-02 14:33 ` Meador Inge
2011-05-31 19:19 ` [PATCH v3 2/2] powerpc: add support for MPIC message register API Meador Inge
2011-05-31 19:19 ` Meador Inge
2011-06-17 5:33 ` Benjamin Herrenschmidt
2011-06-17 5:33 ` Benjamin Herrenschmidt
2011-06-17 13:49 ` [openmcapi-dev] " Meador Inge
2011-06-17 16:58 ` Scott Wood
2011-06-17 16:58 ` Scott Wood
2011-06-17 22:58 ` Benjamin Herrenschmidt [this message]
2011-06-20 15:59 ` Scott Wood
2011-06-20 15:59 ` Scott Wood
2011-06-21 7:47 ` Benjamin Herrenschmidt
2011-06-21 7:47 ` Benjamin Herrenschmidt
2011-06-30 3:04 ` [openmcapi-dev] " Meador Inge
2011-06-30 4:19 ` Benjamin Herrenschmidt
2011-06-30 4:19 ` Benjamin Herrenschmidt
2011-06-09 14:44 ` [openmcapi-dev] [PATCH v3 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-06-09 14:44 ` Meador Inge
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=1308351533.32158.61.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=hollis_blanchard@mentor.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meador_inge@mentor.com \
--cc=openmcapi-dev@googlegroups.com \
--cc=scottwood@freescale.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 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.