From: Steven Rostedt <steven@rostedt.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Yury Norov <ynorov@nvidia.com>,
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>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] tracing: Updates for 7.2
Date: Mon, 22 Jun 2026 04:55:47 -0400 [thread overview]
Message-ID: <20260622045547.74e09a59@fedora> (raw)
In-Reply-To: <20260622084017.GY49951@noisy.programming.kicks-ass.net>
On Mon, 22 Jun 2026 10:40:17 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Sat, Jun 20, 2026 at 07:43:53PM -0400, Steven Rostedt wrote:
>
> > I really want to avoid having to add an include for trace_printk when
> > I'm focusing on just finding were the bug happens.
>
> Configure your LSP/clangd enabled editor to auto-add headers? Yes, that
> really is a thing -- now, I hate that particular feature with a passion,
> and I've got it disabled, but if adding headers is difficult, then it
> sounds like this is the thing for you.
It really isn't about me. I personally don't care if I have to add a
patch to include it in kernel.h in my environment. It's just something
that all the other kernel developers will need to now remember to add
(and then remove) the include.
-- Steve
next prev parent reply other threads:[~2026-06-22 8:55 UTC|newest]
Thread overview: 34+ 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-22 12:50 ` Petr Pavlu
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-21 23:16 ` Linus Torvalds
2026-06-22 8:51 ` 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-22 8:40 ` Peter Zijlstra
2026-06-22 8:55 ` Steven Rostedt [this message]
2026-06-19 15:19 ` Yury Norov
2026-06-19 15:40 ` Linus Torvalds
2026-06-19 22:18 ` Yury Norov
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=20260622045547.74e09a59@fedora \
--to=steven@rostedt.org \
--cc=ao.sun@transsion.com \
--cc=bigeasy@linutronix.de \
--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=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rosenp@gmail.com \
--cc=shuvampandey1@gmail.com \
--cc=tglx@linutronix.de \
--cc=tiffany019230@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vineeth@bitbyteword.org \
--cc=yashsuthar983@gmail.com \
--cc=ynorov@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.