From: Yury Norov <yury.norov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yury Norov <yury.norov@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Ao Sun <ao.sun@transsion.com>, David Carlier <devnexen@gmail.com>,
Karl Mehltretter <kmehltretter@gmail.com>,
Martin Kaiser <martin@kaiser.cx>,
Pengpeng Hou <pengpeng@iscas.ac.cn>,
Qian-Yu Lin <tiffany019230@gmail.com>,
Rik van Riel <riel@surriel.com>, Rosen Penev <rosenp@gmail.com>,
Shuvam Pandey <shuvampandey1@gmail.com>,
Vineeth Pillai <vineeth@bitbyteword.org>,
Yash Suthar <yashsuthar983@gmail.com>,
Yu Peng <pengyu@kylinos.cn>
Subject: Re: [GIT PULL] tracing: Updates for 7.2
Date: Fri, 19 Jun 2026 18:18:51 -0400 [thread overview]
Message-ID: <ajXASxXEqs30UW-M@yury> (raw)
In-Reply-To: <CAHk-=wi-3VeFyitR_ut6ERbHO9KEWYtRG4ghSv8_2nVr-W=3LA@mail.gmail.com>
On Fri, Jun 19, 2026 at 08:40:12AM -0700, Linus Torvalds wrote:
> On Fri, 19 Jun 2026 at 08:19, Yury Norov <yury.norov@gmail.com> wrote:
> >
> > The Steven's point is the convenience for developers to throw
> > trace_printk() here and there without including any headers.
>
> Steven's point isn't a point. It's just fantasy.
>
> trace_printk() isn't special. It's not even common. And people who add
> debugging printk's can add a header file to their own hackery, rather
> than hurt everybody else.
OK, then I'll resend my patch. I tested it with build bots against
various architectures and configs, so I believe it's complete.
Your version includes trace_printk.h in linux/trace.h. It looks
reasonable, and it allows to drop explicit trace_printk.h
inclusion from:
- kernel/trace/trace.c;
- kernel/trace/trace_events_trigger.c;
- kernel/trace/trace_functions.c;
- kernel/trace/trace_printk.c.
With that, the total number of files including the trace_printk.h
is 30, which looks reasonable.
I need a couple days to get feedback from build bots, so not sure I'll
submit it before the end of the week.
If somebody wants to give it a try, check here:
https://github.com/norov/linux/tree/trace_printk
Thanks,
Yury
next prev parent reply other threads:[~2026-06-19 22:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 22:01 [GIT PULL] tracing: Updates for 7.2 Steven Rostedt
2026-06-19 4:23 ` Linus Torvalds
2026-06-19 12:15 ` Steven Rostedt
2026-06-19 14:35 ` Linus Torvalds
2026-06-19 15:40 ` Sebastian Andrzej Siewior
2026-06-19 15:43 ` Linus Torvalds
2026-06-19 18:30 ` Sebastian Andrzej Siewior
2026-06-19 19:07 ` Linus Torvalds
2026-06-19 20:28 ` Thomas Gleixner
2026-06-19 20:55 ` Linus Torvalds
2026-06-20 9:22 ` Willy Tarreau
2026-06-19 22:28 ` Linus Torvalds
2026-06-19 15:54 ` Steven Rostedt
2026-06-19 16:29 ` Linus Torvalds
2026-06-21 20:26 ` Agatha Isabelle Moreira
2026-06-21 20:51 ` Linus Torvalds
2026-06-21 21:19 ` Steven Rostedt
2026-06-20 20:24 ` Julia Lawall
2026-06-21 20:34 ` Agatha Isabelle Moreira
2026-06-20 22:19 ` Steven Rostedt
2026-06-20 22:39 ` Linus Torvalds
2026-06-20 23:43 ` Steven Rostedt
2026-06-21 0:18 ` Linus Torvalds
2026-06-21 6:34 ` Steven Rostedt
2026-06-21 7:10 ` Steven Rostedt
2026-06-19 15:19 ` Yury Norov
2026-06-19 15:40 ` Linus Torvalds
2026-06-19 22:18 ` Yury Norov [this message]
2026-06-19 4:38 ` pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ajXASxXEqs30UW-M@yury \
--to=yury.norov@gmail.com \
--cc=ao.sun@transsion.com \
--cc=devnexen@gmail.com \
--cc=kmehltretter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pengpeng@iscas.ac.cn \
--cc=pengyu@kylinos.cn \
--cc=riel@surriel.com \
--cc=rosenp@gmail.com \
--cc=rostedt@goodmis.org \
--cc=shuvampandey1@gmail.com \
--cc=tiffany019230@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vineeth@bitbyteword.org \
--cc=yashsuthar983@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox