From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: linux-kernel@vger.kernel.org, jolsa@kernel.org, acme@redhat.com,
stable@vger.kernel.org, Adrian Hunter <adrian.hunter@intel.com>,
Borislav Petkov <bp@alien8.de>, David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] perf tools: unbreak perf record for arm/arm64
Date: Mon, 9 Oct 2017 11:51:59 +0100 [thread overview]
Message-ID: <20171009105158.GB10055@leverpostej> (raw)
In-Reply-To: <20171009102159.GA6882@arm.com>
On Mon, Oct 09, 2017 at 11:22:00AM +0100, Will Deacon wrote:
> It sucks that we haven't noticed this being broken for so long, but I can
> confirm that this fixes the issue:
>
> Acked-by: Will Deacon <will.deacon@arm.com>
> Tested-by Will Deacon <will.deacon@arm.com>
Cheers.
> Any chance we can get this into 4.14? You'll probably need to do some
> stable backports too, since this is a bit spread out.
FWIW, I'm happy to do the backport(s) to stable.
As long as the Fixes tag and stable Cc are kept, I should get pinged by
the stable maintainers if/when the patch fails to apply.
Thanks,
Mark.
next prev parent reply other threads:[~2017-10-09 10:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 18:38 [PATCH] perf tools: unbreak perf record for arm/arm64 Mark Rutland
2017-10-09 9:38 ` Jiri Olsa
2017-10-09 10:22 ` Will Deacon
2017-10-09 10:51 ` Mark Rutland [this message]
2017-10-09 19:00 ` Arnaldo Carvalho de Melo
2017-10-09 19:02 ` Will Deacon
2017-10-10 17:28 ` [tip:perf/urgent] perf pmu: Unbreak perf record for arm/arm64 with events with explicit PMU tip-bot for Mark Rutland
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=20171009105158.GB10055@leverpostej \
--to=mark.rutland@arm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=stable@vger.kernel.org \
--cc=will.deacon@arm.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