mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [GIT PULL] perf updates
Date: Mon, 05 Apr 2010 18:56:27 +0900	[thread overview]
Message-ID: <4BB9B3CB.8010306@dcl.info.waseda.ac.jp> (raw)
In-Reply-To: <20100404144223.GB5608@nowhere>

On 04/04/10 23:42, Frederic Weisbecker wrote:
 > On Sun, Apr 04, 2010 at 04:36:40PM +0200, Frederic Weisbecker wrote:
 >> Ingo,
 >>
 >> Please pull the perf/core branch that can be found at:
 >>
 >> 
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
 >> 	perf/core
 >>
 >> Thanks,
 >> 	Frederic
 >> ---
 >>
 >> Frederic Weisbecker (2):
 >>        perf: Drop the frame reliablity check
 >>        perf: Fetch hot regs from the template caller
 >>
 >> Arnd Bergmann (1):
 >>        perf_event: Make perf fd non seekable
 >>
 >> Hitoshi Mitake (1):
 >>        Swap inclusion order of util.h and string.h in util/string.c
 >
 >
 > I just did a last minute rebase, just to prepend the title of this
 > one with "perf: "

Ah, sorry, my naming of title was not good...

Thanks,
	Hitoshi

  parent reply	other threads:[~2010-04-05  9:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 14:36 Frederic Weisbecker
2010-04-04 14:36 ` [PATCH 1/4] perf: Drop the frame reliablity check Frederic Weisbecker
2010-04-04 14:36 ` [PATCH 2/4] perf: Fetch hot regs from the template caller Frederic Weisbecker
2010-04-04 14:36 ` [PATCH 3/4] perf_event: Make perf fd non seekable Frederic Weisbecker
2010-04-04 14:36 ` [PATCH 4/4] Swap inclusion order of util.h and string.h in util/string.c Frederic Weisbecker
2010-04-04 14:42 ` [GIT PULL] perf updates Frederic Weisbecker
2010-04-04 19:02   ` Ingo Molnar
2010-04-05  9:56   ` Hitoshi Mitake [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-26 20:06 Ingo Molnar
2019-09-26 23:00 ` pr-tracker-bot
2016-08-06  6:05 Ingo Molnar
2016-05-25 20:18 Ingo Molnar
2015-07-04 11:25 Ingo Molnar
2015-04-18 15:22 Ingo Molnar
2013-11-13 20:58 Ingo Molnar
2012-05-23 19:01 Ingo Molnar
2011-02-26 15:11 [PATCH v2] perf: Fix undefined PyVarObject_HEAD_INIT in python 2.5 Frederic Weisbecker
2011-03-04  0:38 ` [GIT PULL] perf updates Frederic Weisbecker
2011-03-04  7:10   ` Ingo Molnar
2010-06-08 20:13 Frederic Weisbecker
2010-06-08 21:13 ` Ingo Molnar
2010-05-25 13:45 Frederic Weisbecker
2010-05-09 20:43 Frederic Weisbecker
2010-05-10  5:10 ` Frederic Weisbecker
2010-05-10  6:46 ` Ingo Molnar
2010-04-14 15:59 Frederic Weisbecker
2010-03-05 21:55 Frederic Weisbecker
2010-03-10 14:28 ` Ingo Molnar
2010-03-03  6:54 Frederic Weisbecker
2010-02-27 18:25 [GIT PULL] Perf updates Frederic Weisbecker
2009-12-14 16:24 [GIT PULL] perf updates 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=4BB9B3CB.8010306@dcl.info.waseda.ac.jp \
    --to=mitake@dcl.info.waseda.ac.jp \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=arnd@arndb.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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
all inboxes | Powered by JetHome®