public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung.kim@lge.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	Borislav Petkov <bp@alien8.de>, David Ahern <dsahern@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent
Date: Tue, 10 Apr 2012 09:53:48 +0900	[thread overview]
Message-ID: <87sjgcbe5f.fsf@youngshil.aot.lge.com> (raw)
In-Reply-To: <CAFTL4hz19R9heUjEBZMhweTHRuPzr-qf0hN=FLB9eRd-R9cPgg@mail.gmail.com> (Frederic Weisbecker's message of "Mon, 9 Apr 2012 19:22:46 +0200")

Hi, Frederic

On Mon, 9 Apr 2012 19:22:46 +0200, Frederic Weisbecker wrote:
> 2012/4/9 Namhyung Kim <namhyung.kim@lge.com>:
>> Hi, all
>>
>> This is a couple of small changes that I found during the flight back to
>> Korea :). While I'm not finished with reading the whole code, I send what
>> I have now in the hope that it'd help Frederic's unification work somewhat.
>> More might come later as I read the remaining parts.
>>
>> The patch 01 is a workaround to build trace-cmd without installing swig
>> since I don't have an internet access at that time, so it's independent
>> to others and can go separately.
>>
> Nice! I guess this should probably go into trace-cmd tree and then we
> backport later to the lib?
> Or I can carry them myself in the lib.
>

Either way is fine to me.

Thanks,
Namhyung

      reply	other threads:[~2012-04-10  0:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-09  2:54 [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent Namhyung Kim
2012-04-09  2:54 ` [PATCH 1/7] trace-cmd: Add NO_PYTHON option for Makefile Namhyung Kim
2012-04-10 17:36   ` Steven Rostedt
2012-04-09  2:54 ` [PATCH 2/7] parse-events: Fix printk_cmp() Namhyung Kim
2012-04-10 17:36   ` Steven Rostedt
2012-07-06 11:12   ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09  2:54 ` [PATCH 3/7] parse-events: Introduce extend_token() Namhyung Kim
2012-07-06 11:13   ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09  2:54 ` [PATCH 4/7] parse-events: Handle strdup failure cases Namhyung Kim
2012-04-23 15:51   ` Steven Rostedt
2012-04-24  0:35     ` Namhyung Kim
2012-04-24  0:41       ` Steven Rostedt
2012-07-06 11:14   ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09  2:54 ` [PATCH 5/7] parse-events: Fix a possible memory leak Namhyung Kim
2012-04-09  2:54 ` [PATCH 6/7] parse-events: Handle realloc() failure path Namhyung Kim
2012-07-06 11:15   ` [tip:perf/core] tools lib traceevent: " tip-bot for Namhyung Kim
2012-04-09  2:54 ` [PATCH 7/7] parse-events: Fix a possibly wrong memory dereference Namhyung Kim
2012-04-09 17:22 ` [PATCH 0/7] trace-cmd: Small fixes and cleanups on libparsevent Frederic Weisbecker
2012-04-10  0:53   ` Namhyung Kim [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=87sjgcbe5f.fsf@youngshil.aot.lge.com \
    --to=namhyung.kim@lge.com \
    --cc=acme@infradead.org \
    --cc=bp@alien8.de \
    --cc=dsahern@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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