mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <jiada_wang@mentor.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
	<alexander.shishkin@linux.intel.com>, <ak@linux.intel.com>,
	<jolsa@redhat.com>, <sukadev@linux.vnet.ibm.com>,
	<wangnan0@huawei.com>, <ravi.bangoria@linux.vnet.ibm.com>,
	<mhiramat@kernel.org>, <jstancek@redhat.com>,
	<rui.teng@linux.vnet.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <erosca@de.adit-jv.com>,
	Jiada Wang <jiada_wang@mentor.com>
Subject: [PATCH v4 0/1] fix perf build issue when ARCH=x86_64
Date: Sun, 9 Apr 2017 20:02:36 -0700	[thread overview]
Message-ID: <1491793357-14977-1-git-send-email-jiada_wang@mentor.com> (raw)

From: Jiada Wang <jiada_wang@mentor.com>

Changes from v4:
 update changlog to describe the reason of build failure
 replace ARCH with SRCARCH in pmu-events/Build and util/header.c

Changes from v3:
 replace ARCH with SRCARCH in perf

Changes from v2:
 added function purify-arch, transforms both HOSTARCH and ARCH
 to supported values

Jiada Wang (1):
  perf tools: fix perf build with ARCH=x86_64

 tools/perf/Makefile.config | 38 +++++++++++++++++++-------------------
 tools/perf/Makefile.perf   |  2 +-
 tools/perf/arch/Build      |  2 +-
 tools/perf/tests/Build     |  2 +-
 4 files changed, 22 insertions(+), 22 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-10  3:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  3:02 jiada_wang [this message]
2017-04-10  3:02 ` [PATCH v4 1/1] perf tools: fix perf build with ARCH=x86_64 jiada_wang
2017-04-10  8:17   ` Jiri Olsa
2017-06-13 11:06     ` Jiada Wang
2017-06-16 19:38   ` [tip:perf/urgent] perf tools: Fix " tip-bot for Jiada Wang

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=1491793357-14977-1-git-send-email-jiada_wang@mentor.com \
    --to=jiada_wang@mentor.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=erosca@de.adit-jv.com \
    --cc=jolsa@redhat.com \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.vnet.ibm.com \
    --cc=rui.teng@linux.vnet.ibm.com \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=wangnan0@huawei.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

all inboxes | Powered by JetHome®