On 12/18/19 5:11 PM, Darrick J. Wong wrote: > On Wed, Dec 18, 2019 at 04:18:16PM -0600, Eric Sandeen wrote: >> Sparse checker doesn't like kmem.c tracepoints: >> >> kmem.c:18:32: warning: incorrect type in argument 2 (different base types) >> kmem.c:18:32: expected int [signed] flags >> kmem.c:18:32: got restricted xfs_km_flags_t [usertype] flags >> >> So take an xfs_km_flags_t, and cast it to an int when we print it. >> >> Fixes: 0ad95687c3ad ("xfs: add kmem allocation trace points") >> Signed-off-by: Eric Sandeen <sandeen@xxxxxxxxxx> > > Looks ok insofar as cem will eventually kill these off, right? > Reviewed-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> Oh, I guess so - if you want to just wait for that and drop this patch, it's fine. -Eric