Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Patching eglibc for AArch64
Date: Tue, 04 Dec 2012 10:53:17 +0000	[thread overview]
Message-ID: <1354618398.23886.217.camel@phil-desktop> (raw)
In-Reply-To: <50BDC8E4.1010303@linaro.org>

On Tue, 2012-12-04 at 10:56 +0100, Marcin Juszkiewicz wrote:
> W dniu 29.11.2012 12:19, Marcin Juszkiewicz pisze:
> > I would like to merge AArch64 eglibc support into OE-Core. As patch is
> > nearly 0.5MB I provide it in hrw/aarch64-support branch:
> > 
> > http://git.openembedded.org/openembedded-core-contrib/commit/?h=hrw/aarch64-support&id=aaa36e3ae6ff39682555ac6f21384b44d6f631e3
> > 
> > Commit adds two patches which add AArch64 support for 2.16 version of
> > eglibc. Both were merged upstream but with some alterations to fit into
> > trunk properly. As such trunk patches depend on other patches which can
> > alter state of other architectures which I prefer to avoid.
> > 
> > At Linaro we do daily builds of minimal, lamp, sdk images with this patch.
> 
> ping?

Rather than importing a huge patch, can we not just provide a recipe for
eglibc trunk?  Or wait for a 2.17 release and roll it in then.

p.





      parent reply	other threads:[~2012-12-04 11:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29 11:19 Patching eglibc for AArch64 Marcin Juszkiewicz
2012-12-04  9:56 ` Marcin Juszkiewicz
2012-12-04 10:49   ` Richard Purdie
2012-12-04 10:54     ` Marcin Juszkiewicz
2012-12-10 17:20       ` [PATCH] eglibc: add AArch64 support Marcin Juszkiewicz
2012-12-04 10:53   ` Phil Blundell [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=1354618398.23886.217.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=marcin.juszkiewicz@linaro.org \
    --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