From: Andrew Morton <akpm@linux-foundation.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-mm@kvack.org, Konstantin Khlebnikov <koct9i@gmail.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: Re: [PATCH] mm/vmstat: Fix a W=1 clang compiler warning
Date: Thu, 12 Dec 2024 18:24:25 -0800 [thread overview]
Message-ID: <20241212182425.ad1f7894cd0f00b2e34bbaed@linux-foundation.org> (raw)
In-Reply-To: <20241212213126.1269116-1-bvanassche@acm.org>
On Thu, 12 Dec 2024 13:31:26 -0800 Bart Van Assche <bvanassche@acm.org> wrote:
> Fix the following clang compiler warning that is reported if the kernel is
> built with W=1:
>
> ./include/linux/vmstat.h:518:36: error: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Werror,-Wenum-enum-conversion]
> 518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
> | ~~~~~~~~~~~ ^ ~~~
>
> ...
>
> --- a/include/linux/vmstat.h
> +++ b/include/linux/vmstat.h
> @@ -515,7 +515,7 @@ static inline const char *node_stat_name(enum node_stat_item item)
>
> static inline const char *lru_list_name(enum lru_list lru)
> {
> - return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
> + return node_stat_name(NR_LRU_BASE + (enum node_stat_item)lru) + 3; // skip "nr_"
> }
>
Spose so. One always suspects that adding a typecast is a sign that we
screwed things up somehow. The relationship between enums lru_list and
node_stat_item is foggy, and I'm unsure whether this is the place to
make the transition it. Perhaps lru_list_name() should take an
`unsigned int' arg instead.
next prev parent reply other threads:[~2024-12-13 2:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 21:31 [PATCH] mm/vmstat: Fix a W=1 clang compiler warning Bart Van Assche
2024-12-13 2:24 ` Andrew Morton [this message]
2024-12-13 22:01 ` Bart Van Assche
2025-01-22 1:57 ` Ivan Shapovalov
2025-01-22 21:55 ` Bart Van Assche
2025-01-28 21:36 ` Bart Van Assche
2025-01-29 10:22 ` Vlastimil Babka
2025-01-29 17:30 ` Bart Van Assche
2025-01-29 22:46 ` David Laight
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=20241212182425.ad1f7894cd0f00b2e34bbaed@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bvanassche@acm.org \
--cc=koct9i@gmail.com \
--cc=linux-mm@kvack.org \
--cc=nathan@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