From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Will Newton <will.newton@linaro.org>
Cc: <libc-ports@sourceware.org>, Patch Tracking <patches@linaro.org>
Subject: Re: [PATCH v4] ARM: Add Cortex-A15 optimized NEON and VFP memcpy routines, with IFUNC.
Date: Tue, 30 Apr 2013 14:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1304301423580.21969@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CANu=DmiwUKMuBcwMTL9-aFcwEJA5nCr58aT=Go3QS9LLoO8iLw@mail.gmail.com>
On Tue, 30 Apr 2013, Will Newton wrote:
> > libc changes need to go to libc-alpha, and it's not appropriate to put
> > such an architecture-specific change in the toplevel configure script
> > anyway. Any such architecture-specific checks have to go in appropriate
> > sysdeps configure or preconfigure fragments.
>
> Sorry, I had missed the significance of those files, I'll move the
> check there. I assume once I do that there will be no need to send the
> patch to libc-alpha (as it will only be touching ports code)?
Yes, once the patch is entirely within the ARM port it doesn't need to go
to libc-alpha.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2013-04-30 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 9:52 Will Newton
2013-04-30 11:32 ` Joseph S. Myers
2013-04-30 11:46 ` Will Newton
2013-04-30 14:24 ` Joseph S. Myers [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=Pine.LNX.4.64.1304301423580.21969@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).