All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] tune-ppc476.inc: support ppc476
Date: Thu, 19 Jul 2012 09:12:42 -0700	[thread overview]
Message-ID: <500831FA.2090706@linux.intel.com> (raw)
In-Reply-To: <cover.1342461305.git.peter.seebach@windriver.com>

On 07/16/2012 10:58 AM, Peter Seebach wrote:
> One of the BSPs we support uses a 476-family chip, so we have a
> tuning for it in our custom toolchain layer. Sending a tuning upstream
> too because someone else might want it. Has been lightly tested with
> the oe-core toolchain; it at least allows compiles.
>
> The following changes since commit 20405bdab18b7a2b101f818e72863d289d5945e4:
>    Bruce Ashfield (1):
>          linux-yocto/3.0: perf scripting support
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib seebs/ppc476
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/ppc476
>
> Peter Seebach (1):
>    tune-ppc476.inc: Support ppc476
>
>   meta/conf/machine/include/tune-ppc476.inc |   14 ++++++++++++++
>   1 files changed, 14 insertions(+), 0 deletions(-)
>   create mode 100644 meta/conf/machine/include/tune-ppc476.inc
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core

Thanks
	Sau!




      parent reply	other threads:[~2012-07-19 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 17:58 [PATCH 0/1] tune-ppc476.inc: support ppc476 Peter Seebach
2012-07-16 17:58 ` [PATCH 1/1] tune-ppc476.inc: Support ppc476 Peter Seebach
2012-07-16 18:02   ` Khem Raj
2012-07-19 16:12 ` 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=500831FA.2090706@linux.intel.com \
    --to=sgw@linux.intel.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 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.