Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Denys Dmytriyenko <denys@ti.com>
Subject: Re: [PATCH 0/2] Add more tunes for new ARM processors Cortex-A15 and Cortex-A7
Date: Fri, 19 Oct 2012 23:36:58 +0100	[thread overview]
Message-ID: <1350686218.2520.49.camel@ted> (raw)
In-Reply-To: <20121019193829.GA29349@jama.jama.net>

On Fri, 2012-10-19 at 21:38 +0200, Martin Jansa wrote:
> On Fri, Oct 19, 2012 at 12:56:16PM -0400, Denys Dmytriyenko wrote:
> > On Fri, Oct 19, 2012 at 10:44:32AM +0200, Martin Jansa wrote:
> > > On Thu, Oct 18, 2012 at 06:51:56PM -0400, Denys Dmytriyenko wrote:
> > > > From: Denys Dmytriyenko <denys@ti.com>
> > > > 
> > > > The patchset adds 2 more standard tune files for the new ARM MPCore (multicore)
> > > > processors Cortex-A15 and Cortex-A7, as per:
> > > > 
> > > > http://www.arm.com/products/processors/cortex-a/cortex-a15.php
> > > > http://www.arm.com/products/processors/cortex-a/cortex-a7.php
> > > 
> > > Please check this patchset 
> > > http://lists.linuxtogo.org/pipermail/openembedded-core/2012-October/030759.html
> > 
> > Yes, I've seen that patchset. Unfortunately it's still in the queue and is 
> > going through implementation iterations. Once it gets into OE-Core, I'd be 
> 
> Nobody commented on last iteration (except of acks from khem). So I
> don't plan to send another one.

It was made clear that we were concentrating on the release and these
were something we'd come back to afterwards. I also made it very clear
that I'm opposed to something that is repeatedly getting proposed here.
Lets just say it is unlikely I will simply change my mind if people keep
sending it.

I'm trying to get to the point of reviewing the patches that need
attention and give more constructive feedback having cleared the less
problematic ones out the way and shortened the backlog but I'm not there
yet. Ideally I'd like to take a break entirely but sadly that simply
isn't going to happen :(. I'll try and get to these as soon as I can but
there is a substantial queue. 

I'd also point out I'm getting considerable "feedback" as soon as
anything goes into master that destabilises the build so when anything
does merge, fixing fallout is taking priority too.

Cheers,

Richard





  reply	other threads:[~2012-10-19 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 22:51 [PATCH 0/2] Add more tunes for new ARM processors Cortex-A15 and Cortex-A7 Denys Dmytriyenko
2012-10-18 22:51 ` [PATCH 1/2] tune-cortexa15: add tunes for ARM Cortex-A15 Denys Dmytriyenko
2012-10-18 22:51 ` [PATCH 2/2] tune-cortexa7: add tunes for ARM Cortex-A7 Denys Dmytriyenko
2012-10-19  8:44 ` [PATCH 0/2] Add more tunes for new ARM processors Cortex-A15 and Cortex-A7 Martin Jansa
2012-10-19 16:56   ` Denys Dmytriyenko
2012-10-19 19:38     ` Martin Jansa
2012-10-19 22:36       ` Richard Purdie [this message]
2012-10-19 23:20         ` Martin Jansa

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=1350686218.2520.49.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=denys@ti.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox