From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Will Newton <will.newton@linaro.org>
Cc: <libc-ports@sourceware.org>, <patches@linaro.org>
Subject: Re: [PATCH] ARM: Fix clone build for ARMv4
Date: Thu, 23 Jan 2014 16:32:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1401231631540.31884@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1390477771-30826-1-git-send-email-will.newton@linaro.org>
On Thu, 23 Jan 2014, Will Newton wrote:
> ARMv4 does not have the blx instruction, so use the BLX macro which
> handles abstracting this for us.
>
> ports/ChangeLog.arm:
>
> 2014-01-23 Will Newton <will.newton@linaro.org>
>
> [BZ #16499]
> * sysdeps/unix/sysv/linux/arm/clone.S: Use BLX macro instead
> of blx instruction directly.
OK, presuming you've run the testsuite for at least one ARM configuration.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-01-23 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 11:49 Will Newton
2014-01-23 16:32 ` Joseph S. Myers [this message]
2014-01-23 17:31 ` Carlos O'Donell
2014-01-23 18:22 ` Will Newton
2014-01-24 13:17 ` Will Newton
2014-01-25 10:10 ` Mike Frysinger
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=Pine.LNX.4.64.1401231631540.31884@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
--cc=will.newton@linaro.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).