Re: [GIT PULL] tracing: Updates for 7.2

[Linus Torvalds]

On Sat, 20 Jun 2026 at 16:44, Steven Rostedt <steven@xxxxxxxxxxx> wrote:
>
> For debugging it is really useful.

According to that logic, we should put everything in one header file
and call it a day.

Because no, trace_printk() isn't special.

Christ, the only reason *you* think it's so special is because it's
your code and you use it, and the people you interact with use it.

But that's not because it's special - the common issue is *you*, not
trace_printk.

And yes, we're *all* special. Just like our mothers told us. But
because we're *all* special, none of us are.

So no. Stop making arguments based on that "I'm special" argument.

If you can't back it up with numbers - like I did - then you're not
special, you're just a snowflake.

Honestly, the "I'm using it for debugging" is not an argument.

You can damn well use it for debugging and add the header then.

But I personally think that debugging should be done by looking at and
understanding the code. To me, "debugging using printk's" - fancy
printk's or not - is a failure mode, and soemthing you should be
quietly ashamed of, instead of using it as some kind of argument for
making everybody elses kernel worse.

By the time you resort to debugging with printk, adding the
appropriate include just isn't the issue any more.

We're done here. That header gets removed from kernel.h.

                    Linus