From: Greg KH <greg@kroah.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: 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 <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH v4.12.y] perf pmu: Unbreak perf record for arm/arm64 with events with explicit PMU
Date: Tue, 17 Oct 2017 16:09:23 +0200 [thread overview]
Message-ID: <20171017140923.GC1486@kroah.com> (raw)
In-Reply-To: <20171017134149.28576-1-mark.rutland@arm.com>
On Tue, Oct 17, 2017 at 02:41:49PM +0100, Mark Rutland wrote:
> Commit 66ec11919a0f96e936bb731fdbc2851316077d26 upstream.
<snip>
Thanks for the patch, but 4.12 is end-of-life and I'm not doing any more
releases for it.
You should always be able to check this on the front page of kernel.org.
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-17 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 13:41 [PATCH v4.12.y] perf pmu: Unbreak perf record for arm/arm64 with events with explicit PMU Mark Rutland
2017-10-17 14:09 ` Greg KH [this message]
2017-10-17 14:27 ` 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=20171017140923.GC1486@kroah.com \
--to=greg@kroah.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.