From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Hugh Dickins <hughd@google.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] perf: disable mmap2 support
Date: Thu, 10 Oct 2013 11:26:39 -0300 [thread overview]
Message-ID: <20131010142639.GA3790@infradead.org> (raw)
In-Reply-To: <52559A8E.1030101@gmail.com>
Em Wed, Oct 09, 2013 at 12:03:58PM -0600, David Ahern escreveu:
> On 10/9/13 11:40 AM, Stephane Eranian wrote:
> >On Wed, Oct 9, 2013 at 7:19 PM, David Ahern <dsahern@gmail.com> wrote:
> >>On 10/9/13 10:39 AM, Stephane Eranian wrote:
> >You mean:
> >commit 384c671e33a7ddf905f2c60b433b9883f0e5a605
> >Author: David Ahern <dsahern@gmail.com>
> >Date: Sun Sep 22 19:44:58 2013 -0600
> >
> > perf trace: Add mmap2 handler
> >
> >Right?
>
> Yes, a couple of those have 2 commit ids. I pulled the id's from
> acme's perf/core branch
I'm merging my perf/core branch with Ingo's build speedup series, so
I've removed that patch already, will be ok as soon as the disabling is
done in perf/urgent and those branches get merged.
- Arnaldo
next prev parent reply other threads:[~2013-10-10 14:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 16:17 Stephane Eranian
2013-10-09 16:21 ` David Ahern
2013-10-09 16:24 ` Stephane Eranian
2013-10-09 16:39 ` Stephane Eranian
2013-10-09 17:19 ` David Ahern
2013-10-09 17:40 ` Stephane Eranian
2013-10-09 18:03 ` David Ahern
2013-10-10 14:26 ` Arnaldo Carvalho de Melo [this message]
2013-10-11 18:40 ` David Ahern
2013-10-15 12:25 ` Stephane Eranian
2013-10-15 13:12 ` Ingo Molnar
2013-10-15 13:27 ` Stephane Eranian
2013-10-15 13:34 ` Ingo Molnar
2013-10-15 14:32 ` Stephane Eranian
2013-10-15 16:04 ` Ingo Molnar
2013-10-09 19:33 ` Arnaldo Carvalho de Melo
2013-10-10 4:56 ` Ingo Molnar
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=20131010142639.GA3790@infradead.org \
--to=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=hughd@google.com \
--cc=jolsa@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®