From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/2] tracing: A couple more last minute changes
Date: Wed, 06 Mar 2019 05:16:57 -0500 [thread overview]
Message-ID: <20190306101657.474580583@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 85f726a35e504418607b77c5e7da165dc1ea63ce
Tom Zanussi (2):
tracing: Use strncpy instead of memcpy when copying comm for hist triggers
tracing: Use strncpy instead of memcpy when copying comm in trace.c
----
kernel/trace/trace.c | 4 ++--
kernel/trace/trace_events_hist.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
next reply other threads:[~2019-03-06 10:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 10:16 Steven Rostedt [this message]
2019-03-06 10:16 ` [for-next][PATCH 1/2] tracing: Use strncpy instead of memcpy when copying comm for hist triggers Steven Rostedt
2019-03-06 10:16 ` [for-next][PATCH 2/2] tracing: Use strncpy instead of memcpy when copying comm in trace.c 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=20190306101657.474580583@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox