[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2Kaghnu/sPvl0+g@slm.duckdns.org>
Date: Wed, 2 Nov 2022 06:27:46 -1000
From: 'Tejun Heo' <tj@...nel.org>
To: David Laight <David.Laight@...lab.com>
Cc: Jiri Slaby <jirislaby@...nel.org>,
Christoph Hellwig <hch@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Martin Liska <mliska@...e.cz>,
Josef Bacik <josef@...icpanda.com>,
Jens Axboe <axboe@...nel.dk>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
Subject: Re: [PATCH] block/blk-iocost (gcc13): cast enum members to int in
prints
On Wed, Nov 02, 2022 at 08:35:34AM +0000, David Laight wrote:
> I think the enums have to be split.
> There will be other side effects of promoting the constants to 64bit
> that are much more difficult to detect than the warnings from printf.
idk, I think I can just add LLU to everything and it should be fine.
> I'm also not sure whether the type is even consistent for 32bit
> and 64bit builds.
> Casts are (sort of) horrid.
Yeah, I don't think casts are the solution either. Lemme add LLU to
everything and see how it works.
Thanks.
--
tejun
Powered by blists - more mailing lists