From: Shuah Khan <shuah@kernel.org>
To: David Miller <davem@redhat.com>
Cc: tom.hromatka@oracle.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, f.fainelli@gmail.com,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH] selftests: sparc64: Fix to do nothing on non-sparc64
Date: Fri, 15 Jun 2018 10:51:58 -0600 [thread overview]
Message-ID: <fa06cf9a-e38b-df0d-3e15-a8ecff1e923f@kernel.org> (raw)
In-Reply-To: <20180615.094145.334438195653112696.davem@redhat.com>
On 06/15/2018 10:41 AM, David Miller wrote:
> From: Shuah Khan <shuah@kernel.org>
> Date: Fri, 15 Jun 2018 10:33:21 -0600
>
>> On 06/13/2018 11:20 AM, Tom Hromatka wrote:
>>> Thanks, Shuah!
>>>
>>> Tom
>>>
>>>
>>> On 06/12/2018 05:23 PM, Shuah Khan (Samsung OSG) wrote:
>>>> sparc64 test fails with the following errors on non-sparc64 systems. Fix
>>>> the Makefile to do nothing on non-sparc64 systems to suppress the errors:
>>>>
>>>> make run_tests
>>>> adi-test.c: Assembler messages:
>>>> adi-test.c:302: Error: no such instruction: `rd %tick,%r13'
>>>> adi-test.c:304: Error: no such instruction: `rd %tick,%rbp'
>>>> adi-test.c:190: Error: no such instruction: `rd %tick,%rbp'
>>>> adi-test.c:192: Error: no such instruction: `rd %tick,%rdx'
>>>> adi-test.c:273: Error: no such instruction: `rd %tick,%rbx'
>>>> adi-test.c:276: Error: no such instruction: `rd %tick,%rdx'
>>>> adi-test.c:217: Error: no such instruction: `rd %tick,%rbp'
>>>> adi-test.c:220: Error: no such instruction: `rd %tick,%rdx'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> adi-test.c:246: Error: no such instruction: `rd %tick,%rbp'
>>>> adi-test.c:248: Error: no such instruction: `rd %tick,%rdx'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> adi-test.c:79: Error: no such instruction: `rd %tick,%rax'
>>>> <builtin>: recipe for target 'adi-test' failed
>>>> make[1]: *** [adi-test] Error 1
>>>> adi: [FAIL]
>>>> ./drivers_test.sh: 24: ./drivers_test.sh: ./adi-test: not found
>>>> ../lib.mk:73: recipe for target 'run_tests' failed
>>>> make: *** [run_tests] Error 1
>>>>
>>>> Signed-off-by: Shuah Khan (Samsung OSG) <shuah@kernel.org>
>>>
>>> Reviewed-by: Tom Hromatka <tom.hromatka@oracle.com>
>>>
>>
>> get_maintainers didn't include your name for this patch. Would you like to
>> take this fix through sparc tree? It would be good to get this in for
>> 4.18-rc2
>>
>> If so, please let me know if you would like me to resend the patch
>> with Tom's Reviewed-by tag.
>
> I'm very busy, so this time could you merge this for me? Thanks!
>
> Acked-by: David S. Miller <davem@davemloft.net>
>
Okay. I will take care of this.
thanks,
-- Shuah
prev parent reply other threads:[~2018-06-15 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 23:23 Shuah Khan (Samsung OSG)
2018-06-13 17:20 ` Tom Hromatka
2018-06-15 16:33 ` Shuah Khan
2018-06-15 16:41 ` David Miller
2018-06-15 16:51 ` 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=fa06cf9a-e38b-df0d-3e15-a8ecff1e923f@kernel.org \
--to=shuah@kernel.org \
--cc=davem@redhat.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tom.hromatka@oracle.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
Powered by JetHome