From: Dev Jain <dev.jain@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: shuah@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, Catalin.Marinas@arm.com,
will@kernel.org, ryan.roberts@arm.com, Anshuman.Khandual@arm.com,
aneesh.kumar@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/arm64: Fix build warnings for abi
Date: Thu, 29 Aug 2024 11:55:33 +0530 [thread overview]
Message-ID: <5241c418-d5af-46ca-8188-7b67e1640f88@arm.com> (raw)
In-Reply-To: <6e5588d9-c22c-4a94-afce-1274c888403e@sirena.org.uk>
On 8/28/24 16:10, Mark Brown wrote:
> On Tue, Aug 27, 2024 at 10:48:51AM +0530, Dev Jain wrote:
>
>> - ksft_exit_fail_msg("PTRACE_TRACEME", strerror(errno));
>> + ksft_exit_fail_perror("PTRACE_TRACEME");
>>
>> if (raise(SIGSTOP))
>> - ksft_exit_fail_msg("raise(SIGSTOP)", strerror(errno));
>> + ksft_exit_fail_perror("raise(SIGSTOP)");
> The idea with these is to include the error code as well so adding the
> %s would be better.
ksft_exit_fail_perror() can do that thing for us.
>
>> for (i = 9; i < ARRAY_SIZE(gpr_in); i++) {
>> if (gpr_in[i] != gpr_out[i]) {
>> - ksft_print_msg("%s SVE VL %d mismatch in GPR %d: %llx != %llx\n",
>> + ksft_print_msg("%s SVE VL %d mismatch in GPR %d: %lx != %lx\n",
>> cfg->name, sve_vl, i,
>> gpr_in[i], gpr_out[i]);
>> errors++;
> This is a different pattern of warning, it'd be easier to review if each
> patch only followed one pattern. There's no code overlap between the
> changes.
next prev parent reply other threads:[~2024-08-29 6:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 5:18 [PATCH] selftests/arm64: Fix build warnings for abi Dev Jain
2024-08-27 12:33 ` Will Deacon
2024-08-28 3:49 ` Dev Jain
2024-08-28 11:01 ` Mark Brown
2024-08-29 6:28 ` Dev Jain
2024-08-28 10:40 ` Mark Brown
2024-08-29 6:25 ` Dev Jain [this message]
2024-08-29 11:02 ` Mark Brown
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=5241c418-d5af-46ca-8188-7b67e1640f88@arm.com \
--to=dev.jain@arm.com \
--cc=Anshuman.Khandual@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=will@kernel.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