From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Extra message "case 1" in generated patches
Date: Wed, 24 Jun 2015 18:28:37 +0200 [thread overview]
Message-ID: <558ADAB5.8060503@users.sourceforge.net> (raw)
Dear Julia,
It seems that a few additional debug messages were written
into update suggestions like the following from my source
code analysis approach.
diff -u -p a/tools/lib/traceevent/parse-filter.c b/tools/lib/traceevent/parse-filter.c
--- a/tools/lib/traceevent/parse-filter.c
+++ b/tools/lib/traceevent/parse-filter.c
@@ -1239,8 +1239,7 @@ filter_event(struct event_filter *filter
if (filter_type == NULL)
return PEVENT_ERRNO__MEM_ALLOC_FAILED;
- if (filter_type->filter)
- free_arg(filter_type->filter);
+ free_arg(filter_type->filter);
filter_type->filter = arg;
return 0;
case 1
case 1
How do you think about to avoid such information usually?
Regards,
Markus
reply other threads:[~2015-06-24 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=558ADAB5.8060503@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/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