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/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2
Date: Tue, 26 Mar 2019 08:41:43 -0400 [thread overview]
Message-ID: <20190326124143.521905652@goodmis.org> (raw)
Linus,
Three small fixes:
- A fix to a double free in the histogram code
- Uninitialized variable fix
- Use NULL instead of zero fix and spelling fixes
Please pull the latest trace-v5.1-rc2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v5.1-rc2
Tag SHA1: ed41a01c516cdb7f43a2e0fde385f94f06dff5ff
Head SHA1: 9efb85c5cfac7e1f0caae4471446d936ff2163fe
Frank Rowand (1):
tracing: initialize variable in create_dyn_event()
Hariprasad Kelam (1):
ftrace: Fix warning using plain integer as NULL & spelling corrections
Tom Zanussi (1):
tracing: Remove unnecessary var_ref destroy in track_data_destroy()
----
kernel/trace/ftrace.c | 12 ++++++------
kernel/trace/trace_dynevent.c | 2 +-
kernel/trace/trace_events_hist.c | 1 -
3 files changed, 7 insertions(+), 8 deletions(-)
next reply other threads:[~2019-03-26 12:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:41 Steven Rostedt [this message]
2019-03-26 12:41 ` [PATCH 1/3] tracing: Remove unnecessary var_ref destroy in track_data_destroy() Steven Rostedt
2019-03-26 12:41 ` [PATCH 2/3] tracing: initialize variable in create_dyn_event() Steven Rostedt
2019-03-26 12:41 ` [PATCH 3/3] ftrace: Fix warning using plain integer as NULL & spelling corrections Steven Rostedt
2019-03-26 17:48 ` [PATCH 0/3] [GIT PULL] tracing: Minor fixes for 5.1-rc2 Linus Torvalds
2019-03-26 18:48 ` Steven Rostedt
2019-03-26 21:29 ` Linus Torvalds
2019-03-26 21:46 ` 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=20190326124143.521905652@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 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.