From: Tom Zanussi <tzanussi@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
fweisbec@gmail.com, tzanussi@gmail.com, rostedt@goodmis.org,
tglx@linutronix.de, mingo@elte.hu
Subject: [tip:tracing/filters] tracing/filters: use list_for_each_entry_safe
Date: Mon, 23 Mar 2009 08:31:19 GMT [thread overview]
Message-ID: <tip-75c8b417526529d0a7072e4d93ec99dbd483a6f4@git.kernel.org> (raw)
In-Reply-To: <1237796788.7527.35.camel@charm-linux>
Commit-ID: 75c8b417526529d0a7072e4d93ec99dbd483a6f4
Gitweb: http://git.kernel.org/tip/75c8b417526529d0a7072e4d93ec99dbd483a6f4
Author: Tom Zanussi <tzanussi@gmail.com>
AuthorDate: Mon, 23 Mar 2009 03:26:28 -0500
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Mon, 23 Mar 2009 09:28:07 +0100
tracing/filters: use list_for_each_entry_safe
Impact: cleanup
Use list_for_each_entry_safe instead of list_for_each_entry in
find_event_field().
Reported-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Tom Zanussi <tzanussi@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
LKML-Reference: <1237796788.7527.35.camel@charm-linux>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/trace/trace_events_filter.c | 6 ++----
1 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/kernel/trace/trace_events_filter.c b/kernel/trace/trace_events_filter.c
index 1ab20ce..c4a413b 100644
--- a/kernel/trace/trace_events_filter.c
+++ b/kernel/trace/trace_events_filter.c
@@ -147,11 +147,9 @@ int filter_print_preds(struct filter_pred **preds, char *buf)
static struct ftrace_event_field *
find_event_field(struct ftrace_event_call *call, char *name)
{
- struct ftrace_event_field *field;
- struct list_head *entry, *tmp;
+ struct ftrace_event_field *field, *next;
- list_for_each_safe(entry, tmp, &call->fields) {
- field = list_entry(entry, struct ftrace_event_field, link);
+ list_for_each_entry_safe(field, next, &call->fields, link) {
if (!strcmp(field->name, name))
return field;
}
prev parent reply other threads:[~2009-03-23 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 8:26 [PATCH] tracing/filters: use list_for_each_entry_safe Tom Zanussi
2009-03-23 8:30 ` Li Zefan
2009-03-23 8:33 ` Ingo Molnar
2009-03-23 8:31 ` Tom Zanussi [this message]
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=tip-75c8b417526529d0a7072e4d93ec99dbd483a6f4@git.kernel.org \
--to=tzanussi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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