From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/2] tracing: a couple minor for-next fixes
Date: Sun, 10 Nov 2013 23:03:44 -0600 [thread overview]
Message-ID: <cover.1384145701.git.tom.zanussi@linux.intel.com> (raw)
This patchset fixes a couple sparse warnings reported by the 'kbuild
test robot' and removes a redundant function call noticed by Steve
Rostedt.
The following changes since commit 20b72e76c42bc4f0dd091f9faee542ea45ad6b5e:
Merge branch 'trace/ftrace/core' into trace/for-next (2013-11-06 22:58:52 -0500)
are available in the git repository at:
git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/tracing-next-fixes
http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/tracing-next-fixes
Tom Zanussi (2):
tracing: Add __rcu to enter/exit_syscall_files
tracing: Remove redundant destroy_call_preds() call
kernel/trace/trace.h | 4 ++--
kernel/trace/trace_events.c | 1 -
2 files changed, 2 insertions(+), 3 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-11-11 5:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 5:03 Tom Zanussi [this message]
2013-11-11 5:03 ` [PATCH 1/2] tracing: Add __rcu to enter/exit_syscall_files Tom Zanussi
2013-11-11 5:03 ` [PATCH 2/2] tracing: Remove redundant destroy_call_preds() call Tom Zanussi
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=cover.1384145701.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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