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: Wed, 26 Feb 2025 19:12:35 -0500	[thread overview]
Message-ID: <20250227001235.355892523@goodmis.org> (raw)

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

Head SHA1: 77feaf4a2efb078f4f8c703dce5918c0ce08b7e9


Masami Hiramatsu (Google) (2):
      mm/memblock: Add reserved memory release function
      tracing: Freeable reserved ring buffer

Steven Rostedt (1):
      tracing: Add traceoff_after_boot option

----
 Documentation/admin-guide/kernel-parameters.txt |  9 ++++
 include/linux/mm.h                              |  1 +
 kernel/trace/trace.c                            | 24 ++++++++-
 kernel/trace/trace.h                            |  1 +
 mm/memblock.c                                   | 66 ++++++++++++++++++++-----
 5 files changed, 88 insertions(+), 13 deletions(-)

             reply	other threads:[~2025-02-27  0:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  0:12 Steven Rostedt [this message]
2025-02-27  0:12 ` [for-next][PATCH 1/3] tracing: Add traceoff_after_boot option Steven Rostedt
2025-02-27  0:12 ` [for-next][PATCH 2/3] mm/memblock: Add reserved memory release function Steven Rostedt
2025-02-27  0:12 ` [for-next][PATCH 3/3] tracing: Freeable reserved ring buffer Steven Rostedt
2025-03-06 18:26 ` [for-next][PATCH 0/3] tracing: Updates for v6.15 Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2025-03-07  0:45 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=20250227001235.355892523@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.