From: Catalin Marinas <catalin.marinas@arm.com>
To: open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Will Deacon <will@kernel.org>,
Guo Zhengkui <guozhengkui@vivo.com>,
"moderated list:ARM64 PORT AARCH64 ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Cc: zhengkui_guo@outlook.com
Subject: Re: [PATCH] kselftest/arm64: fix array_size.cocci warning
Date: Wed, 27 Apr 2022 19:40:03 +0100 [thread overview]
Message-ID: <165108479997.3292602.14830911961076617578.b4-ty@arm.com> (raw)
In-Reply-To: <20220419032501.22790-1-guozhengkui@vivo.com>
On Tue, 19 Apr 2022 11:24:51 +0800, Guo Zhengkui wrote:
> Fix the following coccicheck warnings:
> tools/testing/selftests/arm64/mte/check_child_memory.c:110:25-26:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_child_memory.c:88:24-25:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_child_memory.c:90:20-21:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_child_memory.c:147:24-25:
> WARNING: Use ARRAY_SIZE
>
> [...]
Applied to arm64 (for-next/kselftest), thanks!
[1/1] kselftest/arm64: fix array_size.cocci warning
https://git.kernel.org/arm64/c/55a5c18e5dab
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-27 18:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 3:24 [PATCH] kselftest/arm64: fix array_size.cocci warning Guo Zhengkui
2022-04-19 15:55 ` Shuah Khan
2022-04-27 18:40 ` Catalin Marinas [this message]
2022-11-05 7:31 Kang Minchul
2022-11-08 17:38 ` Will Deacon
[not found] <777ce8ba.12e.184705d4211.Coremail.wangkailong@jari.cn>
2022-11-14 19:34 ` Will Deacon
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=165108479997.3292602.14830911961076617578.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=guozhengkui@vivo.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=will@kernel.org \
--cc=zhengkui_guo@outlook.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).