From: Jiri Olsa <jolsa@redhat.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
jolsa@kernel.org
Subject: Re: [4.4] [perf/urgent] perf stat: Fix interval output values
Date: Fri, 28 Oct 2016 16:57:42 +0200 [thread overview]
Message-ID: <20161028145742.GA7580@krava> (raw)
In-Reply-To: <22b261dc-67af-07dd-92b0-46791d6a407f@arm.com>
On Thu, Oct 27, 2016 at 04:39:38PM -0500, Jeremy Linton wrote:
> Hi,
>
> I'm not the original author, but I'd like to request a back port of commit
> 51fd2df1e882a3c2a3f4b6c9ff243a93c9046dba upstream to 4.4.x
>
>
> https://patchwork.kernel.org/patch/8198821/
fine by me.. let me know if you need me to do anything
jirka
next prev parent reply other threads:[~2016-10-28 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 21:39 [4.4] [perf/urgent] perf stat: Fix interval output values Jeremy Linton
2016-10-28 14:57 ` Jiri Olsa [this message]
2016-10-28 15:51 ` Greg Kroah-Hartman
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=20161028145742.GA7580@krava \
--to=jolsa@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeremy.linton@arm.com \
--cc=jolsa@kernel.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 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).