From: "Carlos O'Donell" <carlos@systemhalted.org>
To: Steve McIntyre <steve.mcintyre@linaro.org>,
Marcus Shawcroft <marcus.shawcroft@linaro.org>
Cc: libc-ports@sourceware.org
Subject: Re: [PATCH 2/4] Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache
Date: Wed, 28 Nov 2012 20:58:00 -0000 [thread overview]
Message-ID: <CAE2sS1iYqHVywxBGLW=O-J5ZSFmwUWt1HEH39nM3+kWwAJVZzg@mail.gmail.com> (raw)
In-Reply-To: <20121126150434.GB28791@einval.com>
On Mon, Nov 26, 2012 at 10:04 AM, Steve McIntyre
<steve.mcintyre@linaro.org> wrote:
> Use the new FLAG_AARCH64_LIB64 ldconfig cache tag for AArch64,
> similarly to the way tags are handled for other architectures.
>
> ========================================================
>
> Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache
>
> * sysdeps/unix/sysv/linux/aarch64/dl-cache.h: New file.
>
> Signed-off-by: Steve McIntyre <steve.mcintyre@linaro.org>
Reviewed-by: Carlos O'Donell <carlos@systemhalted.org>
This looks good to me.
Markus, as the AArch64 maintainer, should have the final word and check it in.
Feel free to include my Reviewed-by: in the git commit logs to track reviews.
Cheers,
Carlos.r
next prev parent reply other threads:[~2012-11-28 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 15:02 [PATCH 1/4] Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 Steve McIntyre
2012-11-26 15:05 ` [PATCH 2/4] Check for the FLAG_AARCH64_LIB64 flag in the ldconfig cache Steve McIntyre
2012-11-28 20:58 ` Carlos O'Donell [this message]
2012-11-29 10:40 ` Marcus Shawcroft
2012-11-30 15:01 ` Steve McIntyre
2012-11-30 16:38 ` Carlos O'Donell
2012-12-03 15:19 ` Steve McIntyre
2013-02-08 20:29 ` Andreas Schwab
2012-11-26 15:10 ` [PATCH 3/4] Tag ARM and AArch64 binaries " Steve McIntyre
2012-11-26 16:32 ` [PATCH 1/4] Tag ARM libc6-dependent libraries with FLAG_ELF_LIBC6 Joseph S. Myers
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='CAE2sS1iYqHVywxBGLW=O-J5ZSFmwUWt1HEH39nM3+kWwAJVZzg@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=libc-ports@sourceware.org \
--cc=marcus.shawcroft@linaro.org \
--cc=steve.mcintyre@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).