From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Linux PPC <linuxppc-dev@lists.ozlabs.org>,
cody+local@linux.vnet.ibm.com,
LKML <linux-kernel@vger.kernel.org>,
David.Laight@aculab.com, Anton Blanchard <anton@samba.org>,
Cody P Schafer <cody@linux.vnet.ibm.com>
Subject: [PATCH 0/2] powerpc/perf: fixup 2 patches from the 24x7 series
Date: Wed, 2 Apr 2014 15:10:52 -0700 [thread overview]
Message-ID: <1396476654-20623-1-git-send-email-cody@linux.vnet.ibm.com> (raw)
mpe: these are fixups for 2 patches already in your merge tree (and in benh's next branch).
f3e622941a7cec587c00c0d17ea31514457c63c8 powerpc/perf: Add support for the hv 24x7 interface
edd354ea4a6774bf9f380b0acf30e699070f4e8a powerpc/perf: Add support for the hv gpci (get performance counter info) interface
The only change is to a pr_info() printed when the interface is not detected.
Anton: I'm hesitant to switch these to pr_debug() as they are the only way
users expecting these PMUs to exist to tell why the kernel decided they didn't
have them. As a result, I've kept them as pr_info() instead of converting to
pr_debug().
Cody P Schafer (2):
fixup: "powerpc/perf: Add support for the hv 24x7 interface"
fixup: "powerpc/perf: Add support for the hv gpci (get performance
counter info) interface"
arch/powerpc/perf/hv-24x7.c | 2 +-
arch/powerpc/perf/hv-gpci.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2014-04-02 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 22:10 Cody P Schafer [this message]
2014-04-02 22:10 ` [PATCH 1/2] fixup: "powerpc/perf: Add support for the hv 24x7 interface" Cody P Schafer
2014-04-06 23:48 ` Benjamin Herrenschmidt
2014-04-07 1:22 ` Anton Blanchard
2014-04-02 22:10 ` [PATCH 2/2] fixup: "powerpc/perf: Add support for the hv gpci (get performance counter info) interface" Cody P Schafer
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=1396476654-20623-1-git-send-email-cody@linux.vnet.ibm.com \
--to=cody@linux.vnet.ibm.com \
--cc=David.Laight@aculab.com \
--cc=anton@samba.org \
--cc=cody+local@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
/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).