public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung.kim@lge.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>,
	Namhyung Kim <namhyung@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] perf annotate: Random tiny cleanups
Date: Sat, 3 Mar 2012 16:36:48 -0300	[thread overview]
Message-ID: <20120303193648.GA17066@infradead.org> (raw)
In-Reply-To: <1329986784-4916-1-git-send-email-namhyung.kim@lge.com>

Em Thu, Feb 23, 2012 at 05:46:19PM +0900, Namhyung Kim escreveu:
> Hello,
> 
> This is a patchset tries to fix and improve what I found during code reading.
> Please take a look and consider applying. Comments are welcome, of course.

Thanks, applied all of them,

- Arnaldo

      parent reply	other threads:[~2012-03-03 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  8:46 [PATCH 0/5] perf annotate: Random tiny cleanups Namhyung Kim
2012-02-23  8:46 ` [PATCH 1/5] perf annotate: Print asm code as blue when source code is displayed Namhyung Kim
2012-03-05 16:20   ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-02-23  8:46 ` [PATCH 2/5] perf annotate: Handle lower case key code in annotate_browser__run() Namhyung Kim
2012-03-05 16:21   ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-02-23  8:46 ` [PATCH 3/5] perf annotate: Restore title when came back to original symbol Namhyung Kim
2012-03-05 16:22   ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-02-23  8:46 ` [PATCH 4/5] perf annotate: Fix help string on tui Namhyung Kim
2012-03-05 16:23   ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-02-23  8:46 ` [PATCH 5/5] perf annotate: Add missing newline on error message Namhyung Kim
2012-03-05 16:23   ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-03-03 19:36 ` Arnaldo Carvalho de Melo [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=20120303193648.GA17066@infradead.org \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@gmail.com \
    --cc=paulus@samba.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