mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: avagin@gmail.com
Cc: Andrew Vagin <avagin@openvz.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] trace: don't print an extra separator of flags
Date: Mon, 20 Feb 2012 14:47:56 -0500	[thread overview]
Message-ID: <1329767276.25686.40.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4F42A158.4090501@gmail.com>

On Mon, 2012-02-20 at 23:39 +0400, avagin@gmail.com wrote:
> On 02/20/2012 10:09 PM, Steven Rostedt wrote:
> > On Sun, 2012-02-19 at 14:16 +0300, Andrew Vagin wrote:
> >> From: Andrey Vagin<avagin@openvz.org>
> >>
> >> It occurs if __print_flags is used more than once
> >
> > Hi, which tracepoint does this? I like to see what the issue is.
> 
> The mainstream kernel doesn't have such trace-point, but I have.

Could you send me that patch. Or a change to the kernel that shows the
problem.

> 
> Do you want to say that this bug should not be fixed in this case? :)

No, if it is a issue with the infrastructure, even though nothing
triggers the problem, it should still be fixed, especially if new code
in the future will be triggering it.

-- Steve



  reply	other threads:[~2012-02-20 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 11:16 Andrew Vagin
2012-02-20 18:09 ` Steven Rostedt
2012-02-20 19:39   ` avagin
2012-02-20 19:47     ` Steven Rostedt [this message]
2012-02-20 20:43       ` [PATCH] " Andrew Vagin
2012-02-21  1:18         ` Steven Rostedt
2012-02-27  9:31 ` [tip:perf/core] tracing: Don't " tip-bot for Andrey Vagin

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=1329767276.25686.40.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=avagin@gmail.com \
    --cc=avagin@openvz.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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

all inboxes | Powered by JetHome®