From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: usama.anjum@collabora.com, Shuah Khan <shuah@kernel.org>,
David Hildenbrand <david@redhat.com>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jason Gunthorpe <jgg@ziepe.ca>,
John Hubbard <jhubbard@nvidia.com>, Peter Xu <peterx@redhat.com>,
Leon Romanovsky <leon@kernel.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-riscv@lists.infradead.org,
kevin.brodsky@arm.com, kernel@collabora.com
Subject: Re: [PATCH v3 0/8] selftests/mm: Add compiler flags and fix found warnings
Date: Mon, 25 Aug 2025 12:14:52 +0500 [thread overview]
Message-ID: <a3928ec4-8c2f-4f04-bab4-9ef5c87c57de@collabora.com> (raw)
In-Reply-To: <20250822174259.bf4ed76a0da7d0d6f80ba2c1@linux-foundation.org>
On 8/23/25 5:42 AM, Andrew Morton wrote:
> On Fri, 22 Aug 2025 13:20:57 +0500 Muhammad Usama Anjum <usama.anjum@collabora.com> wrote:
>
>> Recently, I reviewed a patch on the mm/kselftest mailing list about a
>> test which had obvious type mismatch fix in it. It was strange why that
>> wasn't caught during development and when patch was accepted. This led
>> me to discover that those extra compiler options to catch these warnings
>> aren't being used. When I added them, I found tens of warnings in just
>> mm suite.
>>
>> In this series, I'm adding these flags and fixing those warnings. In the
>> last try several months ago [1], I'd patches for individual tests. I've
>> made patches better by grouping the same type of fixes together. Hence
>> there is no changelog for individual patches.
>
> I think it would be best to avoid adding warnings to selftests which
> aren't present in the main kernel code. If only to avoid surprising
> people over what isn't permissible in selftests/.
>
> In particular, there's an expectation that we can do
>
> #else
> static inline int some_stub(type1 arg1, type2 arg2)
> {
> }
> #endif
>
> without warning. We do this extensively.
I'm only adding -Wunreachable-code -Wunused flags now. The above shouldn't
cause any warnings. I'll double check again in next series.
>
> Also, please be aware that there's already a patch in mm-new which
> centralizes selftests' __maybe_unused definition.
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/selftests-centralise-maybe-unused-definition-in-kselftesth.patch
I'll rebase on top of it and send again.
--
---
Thanks,
Usama
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2025-08-25 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 8:20 [PATCH v3 0/8] selftests/mm: Add compiler flags and fix found warnings Muhammad Usama Anjum
2025-08-22 8:20 ` [PATCH v3 1/8] selftests/mm: Add -Wunreachable-code and fix warnings Muhammad Usama Anjum
2025-08-22 17:08 ` Zi Yan
2025-08-26 8:33 ` Kevin Brodsky
2025-08-22 8:20 ` [PATCH v3 2/8] selftests/mm: protection_keys: Fix dead code Muhammad Usama Anjum
2025-08-22 17:11 ` Zi Yan
2025-08-22 8:21 ` [PATCH v3 3/8] selftests: kselftest.h: Add unused macro Muhammad Usama Anjum
2025-08-22 8:21 ` [PATCH v3 4/8] selftests/mm: Add -Wunused family of flags Muhammad Usama Anjum
2025-08-25 18:21 ` John Hubbard
2025-08-26 7:45 ` David Hildenbrand
2025-08-22 8:21 ` [PATCH v3 5/8] selftests/mm: Remove unused parameters Muhammad Usama Anjum
2025-08-22 8:21 ` [PATCH v3 6/8] selftests/mm: Fix unused parameter warnings for different architectures Muhammad Usama Anjum
2025-08-22 8:21 ` [PATCH v3 7/8] selftests/mm: mark variable unused with macro Muhammad Usama Anjum
2025-08-22 8:21 ` [PATCH v3 8/8] selftests/mm: pkey-helpers: Remove duplicate __maybe_unused Muhammad Usama Anjum
2025-08-23 0:42 ` [PATCH v3 0/8] selftests/mm: Add compiler flags and fix found warnings Andrew Morton
2025-08-25 7:14 ` Muhammad Usama Anjum [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=a3928ec4-8c2f-4f04-bab4-9ef5c87c57de@collabora.com \
--to=usama.anjum@collabora.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kernel@collabora.com \
--cc=kevin.brodsky@arm.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=npache@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.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).