All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Tom Zanussi <tzanussi@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] tracing/filters: use strcmp() instead of strncmp()
Date: Tue, 08 Sep 2009 22:00:52 -0400	[thread overview]
Message-ID: <1252461652.11070.4.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4AA70315.7010600@cn.fujitsu.com>

On Wed, 2009-09-09 at 09:21 +0800, Li Zefan wrote:
> > Not sure this is an issue. I may be a little out of context here, but
> > isn't addr coming from the event? The event is made in the kernel and
> > should be fine?
> > 
> > What ever the case, the bug you originally mentioned is still there (I
> > just tried it out on the latest tip). That is, name == et will match
> > "eth0".
> > 
> 
> Strange. I fixed it with this commit:
> 
> ========
> commit 7d536cb3fb9993bdcd5a2fbaa6b0670ded4e101c
> Author: Li Zefan <lizf@cn.fujitsu.com>
> Date:   Thu Jul 16 10:54:02 2009 +0800
> 
>     tracing/events: record the size of dynamic arrays

My fault, I booted into the wrong (older) kernel when I did my test.

Sorry for the noise.

-- Steve



      reply	other threads:[~2009-09-09  2:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  8:41 [PATCH 2/2] tracing/filters: use strcmp() instead of strncmp() Li Zefan
2009-05-29 13:51 ` Frédéric Weisbecker
2009-05-30  9:06   ` Li Zefan
2009-05-30 13:52     ` Frederic Weisbecker
2009-05-31  8:27       ` Li Zefan
2009-05-31 13:28         ` Frederic Weisbecker
2009-06-01  5:45           ` Li Zefan
2009-06-01 13:09             ` Frederic Weisbecker
2009-06-02  0:55               ` Li Zefan
2009-09-08  3:03                 ` Steven Rostedt
2009-09-09  1:21                   ` Li Zefan
2009-09-09  2:00                     ` Steven Rostedt [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=1252461652.11070.4.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --cc=tzanussi@gmail.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 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.