Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Andy Voltz <andy.voltz@timesys.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune-cortexa*.inc: fix tunings for cortex a5, a7, a8, a9, a15 machines.
Date: Wed, 12 Jun 2013 10:57:23 -0700	[thread overview]
Message-ID: <51B8B683.7020402@linux.intel.com> (raw)
In-Reply-To: <20130612171354.GC12032@timesys.com>

On 06/12/2013 10:13 AM, Andy Voltz wrote:
> Hi Saul,
>
> On Wed, Jun 12, 2013 at 12:57:20PM -0400, Saul Wold wrote:
>> On 06/12/2013 09:38 AM, Andy Voltz wrote:
>>> Using CORTEX_ID variable reference in the tuning overrides did not work.
>>> This reverts those changes, and adds a tuning file for the cortex-a5.
>>>
>>> Revert "tune-cortexa5.inc: Add tune file for cortex-a5"
>>> Revert "tune-cortexa.inc: create a common include for cortex-a armv7a tuning"
>>>
>> Andy, does this patch supersede your -mtune not -mcpu patch?  I seem to
>> have some trouble applying this patch.
>>
>
> Yes. Sorry I thought that patch was NACK/dead.
>
>> It might be best to provide a series that includes the reverts with
>> appropriate commit messages.
>>
>
> Sure, I can send as a series.
>

Don't worry about it, seems RP already merged it into master, I must 
have had too much junk in my Master_under_test branch and had not 
reverted the right stuff.

Sau!

> Regards
>


      reply	other threads:[~2013-06-12 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 16:38 [PATCH] tune-cortexa*.inc: fix tunings for cortex a5, a7, a8, a9, a15 machines Andy Voltz
2013-06-12 16:47 ` Otavio Salvador
2013-06-12 16:47 ` Martin Jansa
2013-06-12 16:57 ` Saul Wold
2013-06-12 17:13   ` Andy Voltz
2013-06-12 17:57     ` Saul Wold [this message]

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=51B8B683.7020402@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=andy.voltz@timesys.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