From: Li Zefan <lizefan@huawei.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] tracing: Shrink the size of struct ftrace_event_field
Date: Mon, 29 Jul 2013 10:10:12 +0800 [thread overview]
Message-ID: <51F5CF04.6080306@huawei.com> (raw)
In-Reply-To: <20130727084528.GA6923@pd.tnic>
>>> static int __trace_define_field(struct list_head *head, const char *type,
>>> const char *name, int offset, int size,
>>> int is_signed, int filter_type)
>>> @@ -120,13 +123,16 @@ static int __trace_define_field(struct list_head *head, const char *type,
>>> field->type = type;
>>>
>>> if (filter_type == FILTER_OTHER)
>>> - field->filter_type = filter_assign_type(type);
>>> - else
>>> - field->filter_type = filter_type;
>>> + filter_type = filter_assign_type(type);
>>>
>>> + field->filter_type = filter_type;
>>> field->offset = offset;
>>> field->size = size;
>>> - field->is_signed = is_signed;
>>> + field->is_signed = !!is_signed;
>>> +
>>> + VERIFY_SIZE(filter_type);
>>> + VERIFY_SIZE(offset);
>>> + VERIFY_SIZE(size);
>
> Isn't this wrap-a-macro-with-another-more-obscure-macro not a bit too
> much?
>
> I mean,
> WARN_ON(filter_type > field->filter_type)
>
> is much more readable than VERIFY_SIZE IMO.
>
Oh, right. Using macro is a bit excessive here.
next prev parent reply other threads:[~2013-07-29 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 2:27 [PATCH 1/2][RESEND] tracing/syscalls: Annotate raw_init function with __init Li Zefan
2013-07-25 2:28 ` [PATCH 2/2][RESEND] tracing: Shrink the size of struct ftrace_event_field Li Zefan
2013-07-26 15:09 ` Steven Rostedt
2013-07-27 3:13 ` Li Zefan
2013-07-27 3:32 ` [PATCH v2 2/2] " Li Zefan
2013-07-27 3:47 ` Steven Rostedt
2013-07-27 8:45 ` Borislav Petkov
2013-07-27 11:35 ` Steven Rostedt
2013-07-27 16:19 ` Borislav Petkov
2013-07-29 2:14 ` [PATCH v3 " Li Zefan
2013-07-29 2:10 ` Li Zefan [this message]
2013-07-26 14:23 ` [PATCH 1/2][RESEND] tracing/syscalls: Annotate raw_init function with __init Steven Rostedt
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=51F5CF04.6080306@huawei.com \
--to=lizefan@huawei.com \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.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