public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Zhaolei <zhaolei@cn.fujitsu.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Breaks the redundant loop in kernel/marker.c
Date: Mon, 20 Oct 2008 08:52:05 +0200	[thread overview]
Message-ID: <20081020065205.GA12927@elte.hu> (raw)
In-Reply-To: <48FC273B.3030300@cn.fujitsu.com>


* Zhaolei <zhaolei@cn.fujitsu.com> wrote:

> Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> ---
>  kernel/marker.c |    3 +--
>  1 files changed, 1 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/marker.c b/kernel/marker.c
> index 7d1faec..2c3172d 100644
> --- a/kernel/marker.c
> +++ b/kernel/marker.c
> @@ -836,8 +836,6 @@ void *marker_get_private_data(const char *name, marker_probe_func *probe,
>  			if (!e->ptype) {
>  				if (num == 0 && e->single.func == probe)
>  					return e->single.probe_private;
> -				else
> -					break;
>  			} else {
>  				struct marker_probe_closure *closure;
>  				int match = 0;
> @@ -849,6 +847,7 @@ void *marker_get_private_data(const char *name, marker_probe_func *probe,
>  						return closure[i].probe_private;
>  				}
>  			}
> +			break;
>  		}
>  	}
>  	return ERR_PTR(-ENOENT);

hm, could you describe the necessity of this patch some more? This has 
the change to change behavior, which might even be a bugfix: is there 
any chance that the closure-loop in the e->ptype != NULL branch does not 
exit? Before your patch we'd continue the iteration - which _probably_ 
does not lead to any more matches (e->name is supposed to be unique).

	Ingo

  reply	other threads:[~2008-10-20  6:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  6:37 [PATCH] Breaks the redundant loop in kernel/marker.c Zhaolei
2008-10-20  6:52 ` Ingo Molnar [this message]
2008-10-20  7:17   ` Zhaolei
2008-10-20  7:25     ` Ingo Molnar
2008-10-20 15:38       ` Mathieu Desnoyers
2008-10-22  3:38         ` [PATCH v2] " Zhaolei
2008-10-22  9:15           ` Ingo Molnar

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=20081020065205.GA12927@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=zhaolei@cn.fujitsu.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