Re: [PATCH v2] tracing: Make is_signed_type() compatible with sparse

[Steven Rostedt]

On Wed, 2 Sep 2026 10:04:48 -0700
Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Wed, 2 Sept 2026 at 09:53, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> >
> > If anything, using __bitwise in the field makes things much worse, as you
> > are finding out now.  
> 
> Stop it. __bitwise makes absolutely nothing worse. It's the right
> type. If you are recording a value with any type at all, the type
> should either match the original, or the original type shouldn't
> matter AT ALL.

Relax. I was thinking this was more than for sparse, as I was confused by
David's comment of:

  And, in this case, the value is __bitwise so the 'tooling' doesn't know
  how to display/compare them and you get a compile error. Doesn't seem
  wrong :-)

And was under the impression there was something here that caused a
compiler error. If it's just a sparse bug, then I don't care about it
either.

-- Steve