From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: [PATCH 1/4] tunables: Use glibc.tune.hwcap_mask tunable instead of _dl_hwcap_mask
Date: Wed, 31 May 2017 01:06:00 -0000 [thread overview]
Message-ID: <0bf0ccc8-2bc1-8404-d96a-7eb364503f1c@sourceware.org> (raw)
In-Reply-To: <b9f1b989-4b90-0e26-4f1e-63ac1237c89f@linaro.org>
On Wednesday 31 May 2017 06:18 AM, Adhemerval Zanella wrote:
> I would prefer to maintain consistence and avoid trying to figure out in
> which order should I apply the patches to actually test it. So If I get it
> right, I need to apply v2 patch 1 and patch2, v3 patch 1 to 4, and finally
> v2 patch 5?
I'll just push 4/5 and resend the series. Sorry I didn't realize how
much of a bother this would be :)
Siddhesh
next prev parent reply other threads:[~2017-05-31 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 20:27 [PATCH v3 0/4] aarch64: Allow overriding HWCAP_CPUID feature check Siddhesh Poyarekar
2017-05-25 20:27 ` [PATCH 1/4] tunables: Use glibc.tune.hwcap_mask tunable instead of _dl_hwcap_mask Siddhesh Poyarekar
2017-05-30 21:21 ` Adhemerval Zanella
2017-05-31 0:30 ` Siddhesh Poyarekar
2017-05-31 0:49 ` Adhemerval Zanella
2017-05-31 1:06 ` Siddhesh Poyarekar [this message]
2017-05-25 20:27 ` [PATCH 4/4] aarch64: Add hwcap string routines Siddhesh Poyarekar
2017-05-25 20:27 ` [PATCH 2/4] aarch64: Allow overriding HWCAP_CPUID feature check using HWCAP_MASK Siddhesh Poyarekar
2017-05-25 20:27 ` [PATCH 3/4] Make LD_HWCAP_MASK usable for static binaries Siddhesh Poyarekar
2017-05-26 20:13 ` [PATCH v3 0/4] aarch64: Allow overriding HWCAP_CPUID feature check Steve Ellcey
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=0bf0ccc8-2bc1-8404-d96a-7eb364503f1c@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.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).