From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Milian Wolff <milian.wolff@kdab.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Jiri Olsa <jolsa@kernel.org>, "Liang, Kan" <kan.liang@intel.com>,
"Jin, Yao" <yao.jin@linux.intel.com>
Subject: Re: Inlined functions in perf report
Date: Tue, 20 Dec 2016 18:01:08 +0100 [thread overview]
Message-ID: <20161220170108.GA6467@sesse.net> (raw)
In-Reply-To: <20161220143746.GD32756@kernel.org>
On Tue, Dec 20, 2016 at 11:37:46AM -0300, Arnaldo Carvalho de Melo wrote:
>> Woot. Is this available in git somewhere? (Or if not, what do I apply it on
>> top of?)
> Normally you get it from tip, i.e. from:
>
> git//git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/core
I suppose perf/core here means a branch named perf/core in that git
repository, but it doesn't seem to contain the patches in question.
I tried applying them on top of that branch by wget-ing down the right
messages from marc.info, but somehow, I must have misapplied them
(it was rather painful, especially since they seemingly come out-of-order
in the archives), because the resulting tree didn't compile.
/* Steinar */
--
Homepage: https://www.sesse.net/
next prev parent reply other threads:[~2016-12-20 17:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 11:59 Inlined functions in perf report Steinar H. Gunderson
2016-12-20 12:17 ` Peter Zijlstra
2016-12-20 13:27 ` Milian Wolff
2016-12-20 13:43 ` Steinar H. Gunderson
2016-12-20 14:03 ` Milian Wolff
2016-12-20 13:54 ` Arnaldo Carvalho de Melo
2016-12-20 14:05 ` Milian Wolff
2016-12-20 14:08 ` Steinar H. Gunderson
2016-12-20 14:37 ` Arnaldo Carvalho de Melo
2016-12-20 17:01 ` Steinar H. Gunderson [this message]
2016-12-21 0:53 ` Jin, Yao
2016-12-21 9:58 ` Steinar H. Gunderson
2016-12-21 10:09 ` Milian Wolff
2016-12-21 10:20 ` Steinar H. Gunderson
2016-12-21 22:56 ` Jin, Yao
2016-12-21 22:58 ` Steinar H. Gunderson
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=20161220170108.GA6467@sesse.net \
--to=sgunderson@bigfoot.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.com \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.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 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.