From: Li Zefan <lizf@cn.fujitsu.com>
To: Anirban Sinha <ASinha@zeugmasystems.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [PATCH] : eliminate code duplication in kernel/tracepoint.c
Date: Tue, 25 Aug 2009 13:26:36 +0800 [thread overview]
Message-ID: <4A93760C.4020107@cn.fujitsu.com> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C501EA902E@exchange.ZeugmaSystems.local>
11:57, Anirban Sinha wrote:
> OK, here's the modified patch:
>
>>From 52cea59801ac5b772c49ae995f4df1940a0d88fa Mon Sep 17 00:00:00 2001
> From: Anirban Sinha <asinha@zeugmasystems.com>
> Date: Mon, 24 Aug 2009 20:52:35 -0700
> Subject: cleanup: eliminate code duplication in kernel/tracepoint.c
>
>
> Signed-off-by: Anirban Sinha <asinha@zeugmasystems.com>
> ---
> kernel/tracepoint.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
> index 1ef5d3a..35eed9c 100644
> --- a/kernel/tracepoint.c
> +++ b/kernel/tracepoint.c
> @@ -554,13 +554,9 @@ int tracepoint_module_notify(struct notifier_block
> *self,
>
> switch (val) {
> case MODULE_STATE_COMING:
> - tracepoint_update_probe_range(mod->tracepoints,
> - mod->tracepoints + mod->num_tracepoints);
> - break;
> case MODULE_STATE_GOING:
> tracepoint_update_probe_range(mod->tracepoints,
> mod->tracepoints + mod->num_tracepoints);
> - break;
I still think it's better not to remove this break. every "case"
should have a break or a return, expect for the falling throught
cases.
> }
> return 0;
> }
next prev parent reply other threads:[~2009-08-25 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 23:16 [PATCH] : eliminate code duplication in kernel/tracepoint.c Anirban Sinha
2009-08-25 1:20 ` Li Zefan
2009-08-25 3:57 ` Anirban Sinha
2009-08-25 5:26 ` Li Zefan [this message]
2009-08-25 6:39 ` Ingo Molnar
2009-08-25 14:00 ` Anirban Sinha
2009-08-25 14:18 ` [tip:tracing/core] tracing: Eliminate " tip-bot for Anirban Sinha
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=4A93760C.4020107@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=ASinha@zeugmasystems.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
/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.