From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: "Jiri Slaby (SUSE)" <jirislaby-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Martin Liska <mliska-AlSwsSmVLrQ@public.gmane.org>,
Josef Bacik <josef-DigfWCa+lFGyeJad7bwFQA@public.gmane.org>,
Jens Axboe <axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] block/blk-iocost (gcc13): cast enum members to int in prints
Date: Mon, 31 Oct 2022 05:24:28 -0700 [thread overview]
Message-ID: <Y1++fLJXkeZgtXR2@infradead.org> (raw)
In-Reply-To: <20221031114520.10518-1-jirislaby-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
On Mon, Oct 31, 2022 at 12:45:20PM +0100, Jiri Slaby (SUSE) wrote:
> Cast the enum members to int when printing them.
>
> Alternatively, we can cast them to ulong (to silence gcc < 12) and use %lu.
> Alternatively, we can move VTIME_PER_SEC away from the enum.
Yes, either split the enum or just use a define. But casts are a big
code smell and should be avoided if there is a reasonable alternative.
next prev parent reply other threads:[~2022-10-31 12:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:45 [PATCH] block/blk-iocost (gcc13): cast enum members to int in prints Jiri Slaby (SUSE)
[not found] ` <20221031114520.10518-1-jirislaby-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-10-31 12:24 ` Christoph Hellwig [this message]
2022-10-31 17:57 ` Tejun Heo
[not found] ` <Y2AMcSPAJpj6obSA-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-11-01 5:46 ` Jiri Slaby
[not found] ` <d833ad15-f458-d43d-cab7-de62ff54a939-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-11-01 16:46 ` Tejun Heo
2022-11-02 8:35 ` David Laight
2022-11-02 16:27 ` 'Tejun Heo'
[not found] ` <Y2Kaghnu/sPvl0+g-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-11-02 16:43 ` 'Tejun Heo'
[not found] ` <Y2KePvYRRMOrqzOe-NiLfg/pYEd1N0TnZuCh8vA@public.gmane.org>
2022-12-12 12:14 ` Jiri Slaby
2022-12-12 21:46 ` 'Tejun Heo'
2022-12-13 8:30 ` David Laight
[not found] ` <f5220f08bd7f45248d718f1919503261-1XygrNkDbNvwg4NCKwmqgw@public.gmane.org>
2022-12-13 11:15 ` Jiri Slaby
[not found] ` <9d2ead31-efab-cf49-08d4-1e613382d89f-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-12-13 11:50 ` David Laight
[not found] ` <542d413b9d044474a34b6e7a40d70541-1XygrNkDbNvwg4NCKwmqgw@public.gmane.org>
2022-12-13 12:05 ` Jiri Slaby
[not found] ` <c7539121-c8fc-b4b7-b722-ead833420b2b-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2022-12-13 12:58 ` 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=Y1++fLJXkeZgtXR2@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=axboe-tSWWG44O7X1aa/9Udqfwiw@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=jirislaby-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=josef-DigfWCa+lFGyeJad7bwFQA@public.gmane.org \
--cc=linux-block-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mliska-AlSwsSmVLrQ@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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