From: Mike Frysinger <vapier.adi@gmail.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
David Woodhouse <dwmw2@infradead.org>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Russell King <linux@arm.linux.org.uk>,
Tony Lindgren <tony@atomide.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Eric Miao <eric.miao@canonical.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: [RFC PATCH] arm: drop Execute-In-Place
Date: Thu, 5 May 2011 16:31:11 -0400 [thread overview]
Message-ID: <BANLkTi=qiX9oG=ZMx0nZXrG811L7OZg4ww@mail.gmail.com> (raw)
In-Reply-To: <4DC307D0.3090704@am.sony.com>
On Thu, May 5, 2011 at 16:25, Tim Bird wrote:
> On 05/05/2011 12:27 PM, Mike Frysinger wrote:
>> On Thu, May 5, 2011 at 15:12, Tim Bird wrote:
>>> As for in-tree-ness - I thought the most recent message was to stay
>>> out of tree until the refactoring was over. ;-)
>>
>> to be fair, does this have any relevance whatsoever to NEC parts ?
>> istm that the hindrance here is NEC doing any actual work for
>> mainline. even if there was no refactoring, i find it hard to believe
>> that an NEC port would be posted. if it were actually something that
>> could happen, then they should already be posting patches for *basic*
>> review to get the pieces unrelated to the refactoring worked out.
>> there's no reason this has to be done serially.
>
> Well, OK. I just don't want to lob bombs at NEC and then
> have some poor soul over there get immediately rebuffed, due to
> basic ARM churn. Maybe not having naviengine support upstream
> is my fault, but Sony doesn't make the CPU, so it doesn't seem
> like it should be my job to mainline the chip support. About
> the only thing I have at my disposal is pressure not to buy
> the chip (but this is harder to exercise than one might think.)
i dont have any vested interest either way wrt NEC or ARM/XIP. i was
just trying to highlight what i saw as a red herring.
i think the axiom "post early & post often" holds just as true here.
-mike
next prev parent reply other threads:[~2011-05-05 20:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1304607121-13612-1-git-send-email-plagnioj@jcrosoft.com>
[not found] ` <4DC2E5AA.5010604@am.sony.com>
2011-05-05 18:03 ` [RFC PATCH] arm: drop Execute-In-Place Tim Bird
2011-05-05 18:32 ` David Woodhouse
2011-05-05 18:40 ` Tim Bird
2011-05-05 18:54 ` Nicolas Pitre
2011-05-05 19:04 ` Mike Frysinger
2011-05-05 19:12 ` Tim Bird
2011-05-05 19:27 ` Nicolas Pitre
2011-05-05 20:05 ` Vitaly Wool
2011-05-06 6:07 ` Tony Lindgren
2011-05-05 19:27 ` Mike Frysinger
2011-05-05 20:25 ` Tim Bird
2011-05-05 20:31 ` Mike Frysinger [this message]
2011-05-06 5:17 ` Jean-Christophe PLAGNIOL-VILLARD
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='BANLkTi=qiX9oG=ZMx0nZXrG811L7OZg4ww@mail.gmail.com' \
--to=vapier.adi@gmail.com \
--cc=dwmw2@infradead.org \
--cc=eric.miao@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nicolas.ferre@atmel.com \
--cc=nicolas.pitre@linaro.org \
--cc=plagnioj@jcrosoft.com \
--cc=tim.bird@am.sony.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).