All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/3] tracing: Updates for v6.15
Date: Thu, 06 Mar 2025 19:45:11 -0500	[thread overview]
Message-ID: <20250307004511.688485107@goodmis.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next

Head SHA1: d4ae5070733b114b9431a49c9640437f5e8b2ec5


Christophe JAILLET (1):
      tracing/user_events: Slightly simplify user_seq_show()

Steven Rostedt (1):
      tracing: Update MAINTAINERS file to include tracepoint.c

Thomas Weißschuh (1):
      tracing/user_events: Don't use %pK through printk

----
 MAINTAINERS                      | 1 +
 kernel/trace/trace_events_user.c | 7 ++-----
 2 files changed, 3 insertions(+), 5 deletions(-)

             reply	other threads:[~2025-03-07  0:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07  0:45 Steven Rostedt [this message]
2025-03-07  0:45 ` [for-next][PATCH 1/3] tracing/user_events: Dont use %pK through printk Steven Rostedt
2025-03-07  0:45 ` [for-next][PATCH 2/3] tracing/user_events: Slightly simplify user_seq_show() Steven Rostedt
2025-03-07  0:45 ` [for-next][PATCH 3/3] tracing: Update MAINTAINERS file to include tracepoint.c Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27  0:12 [for-next][PATCH 0/3] tracing: Updates for v6.15 Steven Rostedt
2025-03-06 18:26 ` Steven Rostedt

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=20250307004511.688485107@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    /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.