From: Shuah Khan <shuah@kernel.org>
To: Fathi Boudra <fathi.boudra@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Pratyush Anand <panand@redhat.com>,
linux-kselftest@vger.kernel.org,
shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH 1/1] selftests: breakpoints: allow to cross-compile for aarch64/arm64
Date: Thu, 27 Apr 2017 07:44:43 -0600 [thread overview]
Message-ID: <0dd96239-5fa1-afda-2727-db46f8bb9171@kernel.org> (raw)
In-Reply-To: <CAGNsrLAVOUq2cDcYo1WGFweCkO2LaSV71cXDGhh4Kg2nPDHRLw@mail.gmail.com>
On 04/19/2017 11:31 AM, Fathi Boudra wrote:
> gentle ping
>
> On 22 March 2017 at 20:04, Fathi Boudra <fathi.boudra@linaro.org> wrote:
>> To build breakpoint_test_arm64, ARCH value is only tested for "aarch64".
>> It covers only the native build because it's computed from uname -m output.
>> For cross-compilation, ARCH is set to arm64 and prevent to cross-compile
>> the test.
>> Fix the test to allow both native and cross-compilation of the test.
>>
>> Note: glibc is missing several of the TRAP_* constants in the userspace
>> definitions. Specifically TRAP_BRANCH and TRAP_HWBKPT.
>> See https://sourceware.org/bugzilla/show_bug.cgi?id=21286
>>
>> Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
>> ---
Applied to linux-kselftest next.
thanks for the patch.
-- Shuah
prev parent reply other threads:[~2017-04-27 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 18:04 [PATCH 1/1] selftests: breakpoints: allow to cross-compile for aarch64/arm64 Fathi Boudra
2017-03-30 12:23 ` Naresh Kamboju
2017-04-19 17:31 ` Fathi Boudra
2017-04-19 20:22 ` Shuah Khan
2017-04-27 13:44 ` Shuah Khan [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=0dd96239-5fa1-afda-2727-db46f8bb9171@kernel.org \
--to=shuah@kernel.org \
--cc=fathi.boudra@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=panand@redhat.com \
--cc=shuahkh@osg.samsung.com \
/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 NNTP newsgroup(s).