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>
Subject: [GIT PULL] oprofile: fixes and updates
Date: Tue, 4 Sep 2012 14:28:23 +0200 [thread overview]
Message-ID: <20120904122823.GT8285@erda.amd.com> (raw)
Ingo,
one patch each for perf/urgent and perf/core, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git urgent
and
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git core
Thanks,
-Robert
The following changes since commit fea7a08acb13524b47711625eebea40a0ede69a0:
Linux 3.6-rc3 (2012-08-22 13:29:06 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git core
Robert Richter (2):
oprofile, s390: Fix uninitialized memory access when writing to oprofilefs
oprofile: Remove 'WQ on CPUx, prefer CPUy' warning
arch/s390/oprofile/init.c | 10 +++++-----
drivers/oprofile/cpu_buffer.c | 11 +++--------
2 files changed, 8 insertions(+), 13 deletions(-)
next reply other threads:[~2012-09-04 12:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 12:28 Robert Richter [this message]
2012-09-05 7:55 ` [GIT PULL] oprofile: fixes and 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=20120904122823.GT8285@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
/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