[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <167103701689.7871.5096840115794235278.b4-ty@kernel.dk>
Date: Wed, 14 Dec 2022 09:56:56 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Tejun Heo <tj@...nel.org>,
"Jiri Slaby (SUSE)" <jirislaby@...nel.org>
Cc: linux-kernel@...r.kernel.org, Martin Liska <mliska@...e.cz>,
Josef Bacik <josef@...icpanda.com>, cgroups@...r.kernel.org,
linux-block@...r.kernel.org
Subject: Re: [PATCH v3] block/blk-iocost (gcc13): keep large values in a new enum
On Tue, 13 Dec 2022 13:08:26 +0100, Jiri Slaby (SUSE) wrote:
> Since gcc13, each member of an enum has the same type as the enum [1]. And
> that is inherited from its members. Provided:
> VTIME_PER_SEC_SHIFT = 37,
> VTIME_PER_SEC = 1LLU << VTIME_PER_SEC_SHIFT,
> ...
> AUTOP_CYCLE_NSEC = 10LLU * NSEC_PER_SEC,
> the named type is unsigned long.
>
> [...]
Applied, thanks!
[1/1] block/blk-iocost (gcc13): keep large values in a new enum
commit: ff1cc97b1f4c10db224f276d9615b22835b8c424
Best regards,
--
Jens Axboe
Powered by blists - more mailing lists