linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: mingo@redhat.com, ak@linux.intel.com,
	Michael Ellerman <mpe@ellerman.id.au>,
	Jiri Olsa <jolsa@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: namhyung@kernel.org, maddy@linux.vnet.ibm.com,
	linuxppc-dev@lists.ozlabs.org, <linux-kernel@vger.kernel.org>
Subject: [PATCH v15 03/19] Use __weak definition from <linux/compiler.h>
Date: Wed, 10 Jun 2015 00:25:07 -0700	[thread overview]
Message-ID: <1433921123-25327-4-git-send-email-sukadev@linux.vnet.ibm.com> (raw)
In-Reply-To: <1433921123-25327-1-git-send-email-sukadev@linux.vnet.ibm.com>

Jiri Olsa pointed out, that the <linux/compiler.h> defines the
attribute '__weak'. We might as well use that.

Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Acked-by: Jiri Olsa <jolsa@redhat.com>
---
 tools/perf/util/pmu.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tools/perf/util/pmu.c b/tools/perf/util/pmu.c
index 0fcc624..c6b16b1 100644
--- a/tools/perf/util/pmu.c
+++ b/tools/perf/util/pmu.c
@@ -1,4 +1,5 @@
 #include <linux/list.h>
+#include <linux/compiler.h>
 #include <sys/types.h>
 #include <unistd.h>
 #include <stdio.h>
@@ -436,7 +437,7 @@ static struct cpu_map *pmu_cpumask(const char *name)
 	return cpus;
 }
 
-struct perf_event_attr *__attribute__((weak))
+struct perf_event_attr * __weak
 perf_pmu__get_default_config(struct perf_pmu *pmu __maybe_unused)
 {
 	return NULL;
-- 
1.8.3.1

  parent reply	other threads:[~2015-06-10  7:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-10  7:25 [PATCH V15 00/19] perf, tools: Add support for PMU events in JSON format Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 01/19] perf, tools: Add jsmn `jasmine' JSON parser Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 02/19] perf, tools, jevents: Program to convert JSON file to C style file Sukadev Bhattiprolu
2015-06-10  7:25 ` Sukadev Bhattiprolu [this message]
2015-06-10  7:25 ` [PATCH v15 04/19] perf, tools: Split perf_pmu__new_alias() Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 05/19] perf, tools: Use pmu_events table to create aliases Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 06/19] perf, tools: Support CPU ID matching for Powerpc Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 07/19] perf, tools: Allow events with dot Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 08/19] perf, tools: Support CPU id matching for x86 v2 Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 09/19] perf, tools: Support alias descriptions Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 10/19] perf, tools: Query terminal width and use in perf list Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 11/19] perf, tools: Add a --no-desc flag to " Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 12/19] perf, tools: Add override support for event list CPUID Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 13/19] perf, tools, jevents: Add support for long descriptions Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 14/19] perf, tools: Add alias " Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 15/19] perf, tools: Support long descriptions with perf list Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 16/19] perf, tools, jevents: Add support for event topics Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 17/19] perf, tools: Add support for event list topics Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 18/19] perf, tools: Handle header line in mapfile Sukadev Bhattiprolu
2015-06-10  7:25 ` [PATCH v15 19/19] perf, tools: Add README for info on parsing JSON/map files Sukadev Bhattiprolu
2015-08-11 20:07 ` [PATCH V15 00/19] perf, tools: Add support for PMU events in JSON format Sukadev Bhattiprolu

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=1433921123-25327-4-git-send-email-sukadev@linux.vnet.ibm.com \
    --to=sukadev@linux.vnet.ibm.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=namhyung@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).