public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	oprofile-list <oprofile-list@lists.sourceforge.net>,
	Will Deacon <will.deacon@arm.com>
Subject: [GIT PULL] oprofile: updates for tip/perf/core
Date: Fri, 29 Jun 2012 20:03:04 +0200	[thread overview]
Message-ID: <20120629180304.GZ24632@erda.amd.com> (raw)

Ingo,

it's only one patch (oprofile, perf: Use per-cpu framework), please
pull from:

 git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git core

Note: This pull request implicitly pulls tip/perf/urgent into
tip/perf/core. Hope this is ok to you. This is due to the reason my
patch depends on Will Deacon's patch that is in urgent.

Thanks,

-Robert


The following changes since commit add79461a2a7d964a00b4a2fdaf313c4cf9cf4ec:

  Merge tag 'perf-core-for-mingo' of git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core (2012-06-29 15:11:26 +0200)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git core

Ingo Molnar (1):
      Merge branch 'tip/perf/urgent-2' of git://git.kernel.org/.../rostedt/linux-trace into perf/urgent

Robert Richter (1):
      oprofile, perf: Use per-cpu framework

Steven Rostedt (1):
      ftrace: Make all inline tags also include notrace

Will Deacon (1):
      oprofile: perf: use NR_CPUS instead or nr_cpumask_bits for static array

 drivers/oprofile/oprofile_perf.c |   23 +++++++++++------------
 include/linux/compiler-gcc.h     |    6 +++---
 2 files changed, 14 insertions(+), 15 deletions(-)


             reply	other threads:[~2012-06-29 18:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 18:03 Robert Richter [this message]
2012-07-06 11:08 ` [GIT PULL] oprofile: updates for tip/perf/core 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=20120629180304.GZ24632@erda.amd.com \
    --to=robert.richter@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oprofile-list@lists.sourceforge.net \
    --cc=will.deacon@arm.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