From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] tracing: printk:console fix and __get_str() cleanup
Date: Fri, 1 Jul 2016 20:44:33 -0300 [thread overview]
Message-ID: <cover.1467407618.git.bristot@redhat.com> (raw)
This patch series fixes a problem on printk:console tracepoint
that prints a blank line in the trace output after each printk
message that finishes with '\n'.
It also does some cleanup on __get_str() usage, that
was found while fixing the printk:console tracepoint.
Daniel Bristot de Oliveira (4):
tracing: Use outer () on __get_str() definition
tracing, RAS: Cleanup on __get_str() usage
tracing: Use __get_str() when manipulating strings
printk, tracing: Avoiding unneeded blank lines
fs/nfs/nfs4trace.h | 4 ++--
fs/nfs/nfstrace.h | 4 ++--
include/ras/ras_event.h | 4 ++--
include/trace/events/printk.h | 12 ++++++++++--
include/trace/perf.h | 2 +-
include/trace/trace_events.h | 2 +-
6 files changed, 18 insertions(+), 10 deletions(-)
--
2.7.4
next reply other threads:[~2016-07-01 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 23:44 Daniel Bristot de Oliveira [this message]
2016-07-01 23:44 ` [PATCH 1/4] tracing: Use outer () on __get_str() definition Daniel Bristot de Oliveira
2016-07-01 23:44 ` [PATCH 2/4] tracing, RAS: Cleanup on __get_str() usage Daniel Bristot de Oliveira
2016-07-01 23:44 ` [PATCH 3/4] tracing: Use __get_str() when manipulating strings Daniel Bristot de Oliveira
2016-07-01 23:44 ` [PATCH 4/4] printk, tracing: Avoiding unneeded blank lines Daniel Bristot de Oliveira
2016-07-15 19:53 ` [PATCH 0/4] tracing: printk:console fix and __get_str() cleanup Daniel Bristot de Oliveira
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.1467407618.git.bristot@redhat.com \
--to=bristot@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=trond.myklebust@primarydata.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 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.