lkml.org 
[lkml]   [2022]   [Aug]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
From
On 8/4/22 19:03, kernel test robot wrote:
> sparse warnings: (new ones prefixed by >>)
> fs/nilfs2/segment.c: note: in included file (through include/trace/trace_events.h, include/trace/define_trace.h, include/trace/events/nilfs2.h):
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: cast to restricted blk_opf_t
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer
>>> include/trace/events/nilfs2.h:191:1: sparse: sparse: restricted blk_opf_t degrades to integer
>
> vim +191 include/trace/events/nilfs2.h

Hi Luc and Linus,

I think the above sparse warnings refer to the following macro:

#define is_signed_type(type) (((type)(-1)) < (type)1)

Is the current plan still to modify sparse such that it stops
complaining about the above macro?

See also
https://lore.kernel.org/linux-sparse/20220626095814.7wtma47w4sph7dha@mail/

Thanks,

Bart.

\
 
 \ /
  Last update: 2022-08-05 05:08    [W:0.030 / U:1.564 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site