From: Will Deacon <will@kernel.org>
To: catalin.marinas@arm.com, shuah@kernel.org, wangkailong@jari.cn
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] kselftest/arm64: fix array_size.cocci warning
Date: Mon, 14 Nov 2022 19:34:34 +0000 [thread overview]
Message-ID: <166843703000.2458937.746493234594841296.b4-ty@kernel.org> (raw)
In-Reply-To: <777ce8ba.12e.184705d4211.Coremail.wangkailong@jari.cn>
On Sun, 13 Nov 2022 17:41:10 +0800 (GMT+08:00), wangkailong@jari.cn wrote:
> Fix following coccicheck warning:
>
> tools/testing/selftests/arm64/mte/check_mmap_options.c:64:24-25:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_mmap_options.c:66:20-21:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_mmap_options.c:135:25-26:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_mmap_options.c:96:25-26:
> WARNING: Use ARRAY_SIZE
> tools/testing/selftests/arm64/mte/check_mmap_options.c:190:24-25:
> WARNING: Use ARRAY_SIZE
>
> [...]
Applied to arm64 (for-next/selftests), thanks!
[1/1] kselftest/arm64: fix array_size.cocci warning
https://git.kernel.org/arm64/c/a75df5be8e7b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2022-11-14 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <777ce8ba.12e.184705d4211.Coremail.wangkailong@jari.cn>
2022-11-14 19:34 ` Will Deacon [this message]
2022-11-05 7:31 [PATCH] kselftest/arm64: fix array_size.cocci warning Kang Minchul
2022-11-08 17:38 ` Will Deacon
-- strict thread matches above, loose matches on Subject: below --
2022-04-19 3:24 Guo Zhengkui
2022-04-19 15:55 ` Shuah Khan
2022-04-27 18:40 ` Catalin Marinas
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=166843703000.2458937.746493234594841296.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.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=wangkailong@jari.cn \
/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).