mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/6] [GIT PULL] tracing: Small fixes and clean ups
Date: Thu, 05 Jul 2018 21:06:04 -0400	[thread overview]
Message-ID: <20180706010604.225864413@goodmis.org> (raw)


Linus,

While cleaning out my INBOX, I found a few patches that were lost
in the noise. These are minor bug fixes and clean ups. Those include:

 - Avoiding a string overflow
 - Code that didn't match the comment (but should)
 - A small code optimization (use of a conditional)
 - Quieting printf warnings
 - Nuking unused code
 - Fixing function graph interrupt annotation

Please pull the latest trace-v4.18-rc3 tree, which can be found at:


  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.18-rc3

Tag SHA1: 146913c0aedd504d9230680c8a4708098c4396a6
Head SHA1: 1fe4293f4b8de75824935f8d8e9a99c7fc6873da


Arnd Bergmann (1):
      tracing: Avoid string overflow

Changbin Du (1):
      tracing: Fix missing return symbol in function_graph output

Mathieu Malaterre (1):
      tracing: Use __printf markup to silence compiler

Steven Rostedt (VMware) (1):
      tracing: Make create_filter() code match the comments

Yisheng Xie (1):
      ftrace: Nuke clear_ftrace_function

yuan linyu (1):
      tracing: Optimize trace_buffer_iter() logic

----
 include/linux/ftrace.h               |  2 --
 kernel/trace/ftrace.c                | 13 +------------
 kernel/trace/trace.c                 |  5 +++++
 kernel/trace/trace.h                 |  4 +---
 kernel/trace/trace_events_filter.c   |  5 +++++
 kernel/trace/trace_events_hist.c     |  2 +-
 kernel/trace/trace_functions_graph.c |  5 ++++-
 7 files changed, 17 insertions(+), 19 deletions(-)

                 reply	other threads:[~2018-07-06  1:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180706010604.225864413@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®