public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Daniel Wagner <dwagner@suse.de>,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	Clark Williams <williams@redhat.com>
Subject: [for-next][PATCH 0/3] tracing/tools: Updates for 6.11
Date: Thu, 27 Jun 2024 16:50:22 -0400	[thread overview]
Message-ID: <20240627205022.857212058@goodmis.org> (raw)

In honor of Daniel, I pulled down his repo and noticed that he had
a for-next branch that he has not pushed out yet. So I just took
his branch directly, and will be adding it to the linux-trace.git
tree. It is mostly trivial changes.

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

Head SHA1: 28beb730ee167e505c86d1a8ae239e97d0136b13


Daniel Wagner (1):
      tools: build: use correct lib name for libtracefs feature detection

Luis Claudio R. Goncalves (2):
      rtla/osnoise: Use pretty formatting only on interactive tty
      rtla/osnoise: Better report when histogram is empty

----
 tools/build/feature/Makefile          |  2 +-
 tools/build/feature/test-libtracefs.c |  2 +-
 tools/tracing/rtla/src/osnoise_hist.c | 15 +++++++++++++++
 tools/tracing/rtla/src/osnoise_top.c  | 19 +++++++++++++++----
 4 files changed, 32 insertions(+), 6 deletions(-)

             reply	other threads:[~2024-06-27 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27 20:50 Steven Rostedt [this message]
2024-06-27 20:50 ` [for-next][PATCH 1/3] rtla/osnoise: Use pretty formatting only on interactive tty Steven Rostedt
2024-06-27 20:50 ` [for-next][PATCH 2/3] rtla/osnoise: Better report when histogram is empty Steven Rostedt
2024-06-27 20:50 ` [for-next][PATCH 3/3] tools: build: use correct lib name for libtracefs feature detection 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=20240627205022.857212058@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=dwagner@suse.de \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=williams@redhat.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