linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@infradead.org>,
	David Ahern <daahern@cisco.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
	Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@google.com>,
	Tom Zanussi <tzanussi@gmail.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: [GIT PULL 0/1] perf/urgent fix
Date: Mon, 28 Feb 2011 17:10:21 -0300	[thread overview]
Message-ID: <1298923822-25376-1-git-send-email-acme@infradead.org> (raw)

Hi Ingo,

        Please consider pulling from:

git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux-2.6 perf/urgent

Regards,

- Arnaldo

Arnaldo Carvalho de Melo (1):
  perf symbols: Fix vmlinux path when not using --symfs

 tools/perf/util/symbol.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


             reply	other threads:[~2011-02-28 20:11 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 20:10 Arnaldo Carvalho de Melo [this message]
2011-02-28 20:10 ` [PATCH 1/1] perf symbols: Fix vmlinux path when not using --symfs Arnaldo Carvalho de Melo
2011-03-01  6:22 ` [GIT PULL 0/1] perf/urgent fix Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2017-06-26 19:28 Arnaldo Carvalho de Melo
2017-06-27  7:17 ` Ingo Molnar
2017-03-17 14:03 Arnaldo Carvalho de Melo
2017-03-17 14:14 ` Ingo Molnar
2016-07-28 20:01 Arnaldo Carvalho de Melo
2016-07-29 14:54 ` Ingo Molnar
2016-05-10 14:26 Arnaldo Carvalho de Melo
2016-05-10 20:23 ` Ingo Molnar
2016-04-18 14:15 Arnaldo Carvalho de Melo
2016-04-19  6:42 ` Ingo Molnar
2016-03-29 23:09 Arnaldo Carvalho de Melo
2016-03-30 10:31 ` Ingo Molnar
2016-03-28 20:52 Arnaldo Carvalho de Melo
2016-03-29  8:40 ` Ingo Molnar
2015-10-07 15:42 Arnaldo Carvalho de Melo
2015-10-07 16:33 ` Ingo Molnar
2015-10-08  0:05   ` Michael Ellerman
2015-06-25 16:36 Arnaldo Carvalho de Melo
2015-06-26  8:37 ` Ingo Molnar
2015-06-19 19:51 Arnaldo Carvalho de Melo
2015-06-19 23:08 ` Ingo Molnar
2015-03-05 19:03 Arnaldo Carvalho de Melo
2015-03-05 19:33 ` Ingo Molnar
2014-11-28 21:28 Arnaldo Carvalho de Melo
2014-12-08 10:46 ` Ingo Molnar
2014-10-22 21:06 Arnaldo Carvalho de Melo
2014-10-24  7:47 ` Ingo Molnar
2012-08-21 14:39 Arnaldo Carvalho de Melo
2012-08-21 14:58 ` Ingo Molnar
2012-05-09 17:43 Arnaldo Carvalho de Melo
2012-05-10  8:55 ` Ingo Molnar
2012-04-11 20:57 Arnaldo Carvalho de Melo
2012-04-13  7:49 ` Ingo Molnar
2011-09-29 22:53 Arnaldo Carvalho de Melo
2011-09-30 18:09 ` Ingo Molnar
2011-03-28 18:07 Arnaldo Carvalho de Melo
2011-03-29  7:12 ` Ingo Molnar
2011-03-09 22:57 Arnaldo Carvalho de Melo
2011-03-10  6:34 ` Ingo Molnar
2010-12-06 20:25 Arnaldo Carvalho de Melo
2010-08-18 22:18 Arnaldo Carvalho de Melo
2010-08-19 10:25 ` Ingo Molnar

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=1298923822-25376-1-git-send-email-acme@infradead.org \
    --to=acme@infradead.org \
    --cc=acme@ghostprotocols.net \
    --cc=daahern@cisco.com \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).