From: Namhyung Kim <namhyung.kim@lge.com>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/22] perf tools: Backport of latest changes on trace-cmd's libparseevent
Date: Mon, 11 Jun 2012 11:47:10 +0900 [thread overview]
Message-ID: <4FD55C2E.1020103@lge.com> (raw)
In-Reply-To: <20120531153153.GH13591@infradead.org>
Hi, all
2012-06-01 12:31 AM, Arnaldo Carvalho de Melo wrote:
> Em Thu, May 31, 2012 at 05:22:45PM +0200, Frederic Weisbecker escreveu:
>> On Thu, May 31, 2012 at 12:13:56PM -0300, Arnaldo Carvalho de Melo wrote:
>>> Em Thu, May 31, 2012 at 11:09:46AM -0400, Steven Rostedt escreveu:
>>>> On Thu, 2012-05-31 at 11:52 -0300, Arnaldo Carvalho de Melo wrote:
>>>>> Em Thu, May 31, 2012 at 03:07:26PM +0900, Namhyung Kim escreveu:
>>>>>> It'd be great if you set up a branch for this so that I can continue to
>>>>>> work on it until fully-merged.
>
>>>>> Have you had luck obtaining a git.kernel.org account? It would be better
>>>>> if you used git and maintained such branch :-\
>
>>>> Darn it! I wish I signed his key when I had the chance :-p
>
>>> I did it, Frédéric too, so he should have no problem getting an account,
>>> I think,
>>
>> Except I haven't yet managed to get my korg account back and only Namhyung has
>> signed my key. So I'm not going to be very helpful in this regard ;)
>
> I just checked, he got other sigs, so your chain also should be good to
> go ;-)
>
Now I got an account and setup a tree at
/pub/scm/linux/kernel/git/namhyung/linux-perf.git. I'll work on further
libtraceevent improvement on libtraceeevnt/next branch.
Thanks to all you guys to help me setting this up. :)
next prev parent reply other threads:[~2012-06-11 2:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 2:36 [PATCH 00/22] perf tools: Backport of latest changes on trace-cmd's libparseevent Namhyung Kim
2012-05-23 2:36 ` [PATCH 01/22] lib/traceevent: Let filtering numbers by string use function names Namhyung Kim
2012-05-23 2:36 ` [PATCH 02/22] lib/traceevent: Add support for "%.*s" in bprintk events Namhyung Kim
2012-05-23 2:36 ` [PATCH 03/22] lib/traceevent: Add support to show migrate disable counter Namhyung Kim
2012-05-23 2:36 ` [PATCH 04/22] lib/traceevent: Fix %pM print format arg handling Namhyung Kim
2012-05-23 2:36 ` [PATCH 05/22] lib/traceevent: Allow expressions in __print_symbolic() fields Namhyung Kim
2012-05-24 17:16 ` [tip:perf/urgent] tools lib traceevent: " tip-bot for Stefan Hajnoczi
2012-05-23 2:36 ` [PATCH 06/22] lib/traceevent: Fix trace_printk for long integers Namhyung Kim
2012-05-23 2:36 ` [PATCH 07/22] lib/traceevent: Fix printk_cmp() Namhyung Kim
2012-05-23 2:36 ` [PATCH 08/22] lib/traceevent: Introduce extend_token() Namhyung Kim
2012-05-23 2:36 ` [PATCH 09/22] lib/traceevent: Handle strdup failure cases Namhyung Kim
2012-05-23 2:36 ` [PATCH 10/22] lib/traceevent: Fix a possible memory leak Namhyung Kim
2012-05-24 17:17 ` [tip:perf/urgent] tools lib traceevent: " tip-bot for Namhyung Kim
2012-05-23 2:36 ` [PATCH 11/22] lib/traceevent: Handle realloc() failure path Namhyung Kim
2012-05-23 2:36 ` [PATCH 12/22] lib/traceevent: Fix a possibly wrong memory dereference Namhyung Kim
2012-05-24 17:18 ` [tip:perf/urgent] tools lib traceevent: " tip-bot for Namhyung Kim
2012-05-23 2:36 ` [PATCH 13/22] lib/traceevent: Fix freeing arg on process_dynamic_array() Namhyung Kim
2012-05-24 17:19 ` [tip:perf/urgent] tools lib traceevent: " tip-bot for Namhyung Kim
2012-05-23 2:36 ` [PATCH 14/22] lib/traceevent: Use proper function parameter type Namhyung Kim
2012-05-24 17:19 ` [tip:perf/urgent] tools lib traceevent: " tip-bot for Namhyung Kim
2012-05-23 2:36 ` [PATCH 15/22] lib/traceevent: Pass string type argument to args Namhyung Kim
2012-05-23 2:36 ` [PATCH 16/22] lib/traceevent: Do not call add_event() again if allocation failed Namhyung Kim
2012-05-23 2:36 ` [PATCH 17/22] lib/traceevent: Fix some comments Namhyung Kim
2012-05-23 2:36 ` [PATCH 18/22] lib/traceevent: Check result of malloc() during reading token Namhyung Kim
2012-05-23 2:36 ` [PATCH 19/22] lib/traceevent: Fix signature of create_arg_item() Namhyung Kim
2012-05-24 17:20 ` [tip:perf/urgent] tools lib traceevent: " tip-bot for Namhyung Kim
2012-05-23 2:36 ` [PATCH 20/22] lib/traceevent: Check return value of arg_to_str() Namhyung Kim
2012-05-23 2:36 ` [PATCH 21/22] lib/traceevent: Add missing break in make_bprint_args Namhyung Kim
2012-05-23 2:36 ` [PATCH 22/22] lib/traceevent: Cleanup realloc use Namhyung Kim
2012-05-24 1:08 ` [PATCH 00/22] perf tools: Backport of latest changes on trace-cmd's libparseevent Steven Rostedt
2012-05-31 6:07 ` Namhyung Kim
2012-05-31 14:52 ` Arnaldo Carvalho de Melo
2012-05-31 15:09 ` Steven Rostedt
2012-05-31 15:13 ` Arnaldo Carvalho de Melo
2012-05-31 15:22 ` Frederic Weisbecker
2012-05-31 15:31 ` Arnaldo Carvalho de Melo
2012-06-01 2:48 ` Namhyung Kim
2012-06-11 2:47 ` Namhyung Kim [this message]
2012-06-11 14:17 ` Arnaldo Carvalho de Melo
2012-06-12 6:39 ` Namhyung Kim
2012-06-13 2:39 ` Namhyung Kim
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=4FD55C2E.1020103@lge.com \
--to=namhyung.kim@lge.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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