From: Peter Zijlstra <peterz@infradead.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Paul Mackerras <paulus@samba.org>,
luto@amacapital.net, hpa@linux.intel.com
Subject: Re: [PATCH] perf: Add vm_ops->name call for mmap event name retrieval
Date: Mon, 14 Jul 2014 20:18:46 +0200 [thread overview]
Message-ID: <20140714181846.GJ9918@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140714173755.GH17761@krava.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Mon, Jul 14, 2014 at 07:37:55PM +0200, Jiri Olsa wrote:
> On Mon, Jul 14, 2014 at 06:09:47PM +0200, Peter Zijlstra wrote:
> > On Mon, Jul 14, 2014 at 05:57:19PM +0200, Jiri Olsa wrote:
> > > Following patch added another way to get mmap name:
> > > 78d683e mm, fs: Add vm_ops->name as an alternative to arch_vma_name
> >
> > Please add to your .gitconfig:
> >
> > [core]
> > abbrev = 12
>
> hum, will check
Mandated by Linus, also I've already had 8 char hash collisions, so it
really makes sense.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-07-14 18:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 15:57 [PATCH] perf: Add vm_ops->name call for mmap event name retrieval Jiri Olsa
2014-07-14 16:09 ` Peter Zijlstra
2014-07-14 16:13 ` Peter Zijlstra
2014-07-14 16:14 ` Andy Lutomirski
2014-07-14 16:17 ` Peter Zijlstra
2014-07-14 16:29 ` Andy Lutomirski
2014-07-14 16:34 ` Peter Zijlstra
2014-07-14 17:37 ` Jiri Olsa
2014-07-14 18:18 ` Peter Zijlstra [this message]
2014-07-16 19:21 ` [tip:perf/core] perf: Add vm_ops-> name " tip-bot for Jiri Olsa
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=20140714181846.GJ9918@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hpa@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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.