From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] elf2flt: fix threading apps on ARM noMMU systems
Date: Thu, 25 Aug 2016 15:57:19 +0200 [thread overview]
Message-ID: <20160825155719.059243f6@free-electrons.com> (raw)
In-Reply-To: <20160824210342.GA7164@waldemar-brodkorb.de>
Hello,
On Wed, 24 Aug 2016 23:03:43 +0200, Waldemar Brodkorb wrote:
> See this thread, which explains the problem in detail:
> http://mailman.uclinux.org/pipermail/uclinux-dev//2016-April/052713.html
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> This should be applied to master.
> ---
> ...-relocation-support-for-R_ARM_TARGET-type.patch | 34 ++++++++++++++++++++++
> 1 file changed, 34 insertions(+)
> create mode 100644 package/elf2flt/0001-elf2flt-fix-relocation-support-for-R_ARM_TARGET-type.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-08-25 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 21:03 [Buildroot] [PATCH] elf2flt: fix threading apps on ARM noMMU systems Waldemar Brodkorb
2016-08-25 13:57 ` Thomas Petazzoni [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=20160825155719.059243f6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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