linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
	<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
	<jolsa@redhat.com>, <namhyung@kernel.org>
Cc: <linux-perf-users@vger.kernel.org>, <irogers@google.com>,
	<olsajiri@gmail.com>, <rric@kernel.org>, <ak@linux.intel.com>,
	John Garry <john.garry@huawei.com>
Subject: [PATCH v2 0/2] perf tool versioning fixes
Date: Mon, 21 Feb 2022 21:16:47 +0800	[thread overview]
Message-ID: <1645449409-158238-1-git-send-email-john.garry@huawei.com> (raw)

This series includes a couple of fixes I made from working on a clone of
acme.git

It is based on perf/urgent @ commit b3d971ec2534.

Differences to v1:
- Add patch to fix kernel version tag
- Fix perf out-of-tree build

John Garry (2):
  perf: Fix dependency for version file creation
  perf: Fix version kernel tag

 tools/perf/Makefile.perf         |  4 ++--
 tools/perf/util/PERF-VERSION-GEN | 13 ++++---------
 2 files changed, 6 insertions(+), 11 deletions(-)

-- 
2.26.2


             reply	other threads:[~2022-02-21 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 13:16 John Garry [this message]
2022-02-21 13:16 ` [PATCH v2 1/2] perf: Fix dependency for version file creation John Garry
2022-02-21 13:16 ` [PATCH v2 2/2] perf: Fix version kernel tag John Garry
     [not found]   ` <CAP-5=fXT3VYB2uBXmihuruq==FENLFcFSHMLY0Fk29pRvU-wag@mail.gmail.com>
2022-03-11  8:27     ` John Garry
2022-03-14 22:12       ` Ian Rogers
2022-03-15 11:31         ` John Garry
2022-02-25 19:37 ` [PATCH v2 0/2] perf tool versioning fixes John Garry

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=1645449409-158238-1-git-send-email-john.garry@huawei.com \
    --to=john.garry@huawei.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=olsajiri@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rric@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).