From: Peter Xu <peterx@redhat.com>
To: linux-kernel@vger.kernel.org, srostedt@redhat.com
Cc: peterx@redhat.com
Subject: [PATCH trace-cmd 0/2] better error handling during copy
Date: Tue, 22 Mar 2016 15:40:40 +0800 [thread overview]
Message-ID: <1458632442-6878-1-git-send-email-peterx@redhat.com> (raw)
CCing lkml this time. Hope it's the right way...
For patch 1, it only drops one printf(), which is optional.
For patch 2, it tries to dump more information when we got errors,
and also catches some silence ones.
Peter Xu (2):
trace-cmd-listen: remove useless printf
trace-recorder: better error handling during copy
trace-listen.c | 1 -
trace-recorder.c | 34 ++++++++++++++++++++++++----------
2 files changed, 24 insertions(+), 11 deletions(-)
--
2.4.3
next reply other threads:[~2016-03-22 7:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 7:40 Peter Xu [this message]
2016-03-22 7:40 ` [PATCH trace-cmd 1/2] trace-cmd-listen: remove useless printf Peter Xu
2016-03-22 13:18 ` Steven Rostedt
2016-03-23 6:39 ` Peter Xu
2016-03-22 7:40 ` [PATCH trace-cmd 2/2] trace-recorder: better error handling during copy Peter Xu
2016-03-22 13:19 ` Steven Rostedt
2016-03-23 7:02 ` Peter Xu
2016-03-23 7:05 ` [PATCH trace-cmd v2] " Peter Xu
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=1458632442-6878-1-git-send-email-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srostedt@redhat.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 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®