Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Henning Heinold <h.heinold@tarent.de>
Subject: Re: [PATCH] arm-atomic-gcc patches for oe-stable
Date: Mon, 19 Jul 2010 20:26:06 -0700	[thread overview]
Message-ID: <20100720032606.GC7574@gmail.com> (raw)
In-Reply-To: <1279551515-19474-1-git-send-email-heinold@inf.fu-berlin.de>

On (19/07/10 16:58), heinold@inf.fu-berlin.de wrote:
> From: Henning Heinold <h.heinold@tarent.de>
> 
> Hi,
> 
> this is a backport for the arm-atomic-gcc patches.
> 
> It is the first step to get openjdk into oe-stable.
> 

Acked-by: Khem Raj <raj.khem@gmail.com>

> Bye,
> 
> Henning
> 
> 
> Henning Heinold (1):
>   gcc: backport 4.3.x atomic-patches series from openembedded-dev
> 
>  recipes/gcc/gcc-4.3.1.inc                          |    4 +-
>  .../gcc-4.3.1/debian/armel-atomic-builtins.dpatch  |  350 ++++++++++++++++++++
>  ...90519-arm-eabi-atomic-builtins-unbreak-v2.patch |   52 +++
>  recipes/gcc/gcc-4.3.2.inc                          |    4 +-
>  .../gcc-4.3.2/debian/armel-atomic-builtins.dpatch  |  350 ++++++++++++++++++++
>  ...90519-arm-eabi-atomic-builtins-unbreak-v2.patch |   52 +++
>  recipes/gcc/gcc-4.3.3.inc                          |    2 +
>  .../gcc-4.3.3/debian/armel-atomic-builtins.dpatch  |  350 ++++++++++++++++++++
>  ...90519-arm-eabi-atomic-builtins-unbreak-v2.patch |   52 +++
>  recipes/gcc/gcc-cross-sdk_4.3.1.bb                 |    2 +-
>  recipes/gcc/gcc-cross-sdk_4.3.2.bb                 |    2 +-
>  recipes/gcc/gcc-cross-sdk_4.3.3.bb                 |    2 +-
>  recipes/gcc/gcc-cross_4.3.1.bb                     |    2 +-
>  recipes/gcc/gcc-cross_4.3.2.bb                     |    2 +-
>  recipes/gcc/gcc-cross_4.3.3.bb                     |    2 +-
>  recipes/gcc/gcc_4.3.1.bb                           |    2 +-
>  recipes/gcc/gcc_4.3.2.bb                           |    2 +-
>  recipes/gcc/gcc_4.3.3.bb                           |    2 +-
>  18 files changed, 1223 insertions(+), 11 deletions(-)
>  create mode 100644 recipes/gcc/gcc-4.3.1/debian/armel-atomic-builtins.dpatch
>  create mode 100644 recipes/gcc/gcc-4.3.1/gcc-4.4-20090519-arm-eabi-atomic-builtins-unbreak-v2.patch
>  create mode 100644 recipes/gcc/gcc-4.3.2/debian/armel-atomic-builtins.dpatch
>  create mode 100644 recipes/gcc/gcc-4.3.2/gcc-4.4-20090519-arm-eabi-atomic-builtins-unbreak-v2.patch
>  create mode 100644 recipes/gcc/gcc-4.3.3/debian/armel-atomic-builtins.dpatch
>  create mode 100644 recipes/gcc/gcc-4.3.3/gcc-4.4-20090519-arm-eabi-atomic-builtins-unbreak-v2.patch
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



      parent reply	other threads:[~2010-07-20  3:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 14:58 [PATCH] arm-atomic-gcc patches for oe-stable heinold
2010-07-19 14:58 ` [PATCH] gcc: backport 4.3.x atomic-patches series from openembedded-dev heinold
2010-07-20  3:26   ` Khem Raj
2010-07-20  6:53   ` Stefan Schmidt
2010-07-20  8:06   ` Koen Kooi
2010-07-20  3:26 ` Khem Raj [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=20100720032606.GC7574@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=h.heinold@tarent.de \
    --cc=openembedded-devel@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