Re: [PATCH] blk-iocost: fix seq_printf compile type mismatch error
From: 'Tejun Heo'
Date: Fri Jul 21 2023 - 13:58:32 EST
Hello,
On Fri, Jul 21, 2023 at 08:05:59AM +0000, David Laight wrote:
> In any case it is enough to split the enum.
> If you really need unrelated constants to be defined in an enum
> them maybe use a separate enum for each.
> Using (on one line):
> enum { name = constant };
Yeah, I'm hoping it won't come down to that. Hopefully, we can limp along
like this until we can always assume the new behavior. Right now, the
problem is that both gcc<13 and gcc=13 have to supported when the two assign
different types to the same enum definitions.
Thanks.
--
tejun