From: Stephane Eranian <eranian@google.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH tip] perf/x86: nhm_events_attrs and snb_events_attrs can be static
Date: Tue, 29 Jan 2013 01:31:19 +0100 [thread overview]
Message-ID: <CABPqkBS4Y7y4OPH_5XYcrupGfRat9whT=3B8Fpyo7KuBAHDFfg@mail.gmail.com> (raw)
In-Reply-To: <20130128234620.GA8524@localhost>
On Tue, Jan 29, 2013 at 12:46 AM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
Acked-by: Stephane Eranian <eranian@google.com>
> ---
> arch/x86/kernel/cpu/perf_event_intel.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-next.orig/arch/x86/kernel/cpu/perf_event_intel.c 2013-01-29 07:42:16.238595053 +0800
> +++ linux-next/arch/x86/kernel/cpu/perf_event_intel.c 2013-01-29 07:43:47.678597226 +0800
> @@ -139,12 +139,12 @@ static struct extra_reg intel_snb_extra_
> EVENT_ATTR_STR(mem-loads, mem_ld_nhm, "event=0x0b,umask=0x10,ldlat=3");
> EVENT_ATTR_STR(mem-loads, mem_ld_snb, "event=0xcd,umask=0x1,ldlat=3");
>
> -struct attribute *nhm_events_attrs[] = {
> +static struct attribute *nhm_events_attrs[] = {
> EVENT_PTR(mem_ld_nhm),
> NULL,
> };
>
> -struct attribute *snb_events_attrs[] = {
> +static struct attribute *snb_events_attrs[] = {
> EVENT_PTR(mem_ld_snb),
> NULL,
> };
next prev parent reply other threads:[~2013-01-29 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <510441ca.jKKGS3DOYyOC3gnk%fengguang.wu@intel.com>
[not found] ` <20130127010632.GF12329@localhost>
[not found] ` <CABPqkBR4VCOpBH25yQOnhkOs6c52xEnNe=P4qifDXzr7WBERxw@mail.gmail.com>
2013-01-28 23:46 ` [PATCH tip] perf/x86: nhm_events_attrs and snb_events_attrs can be static Fengguang Wu
2013-01-29 0:31 ` Stephane Eranian [this message]
2013-01-29 9:42 ` [tip:perf/x86] perf/x86: Mark nhm_events_attrsas static tip-bot for Fengguang Wu
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='CABPqkBS4Y7y4OPH_5XYcrupGfRat9whT=3B8Fpyo7KuBAHDFfg@mail.gmail.com' \
--to=eranian@google.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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;
as well as URLs for NNTP newsgroup(s).