All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Kairui Song <kasong@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>, Dave Young <dyoung@redhat.com>
Subject: Re: [RFC PATCH v4] perf/x86: make perf callchain work without CONFIG_FRAME_POINTER
Date: Tue, 7 May 2019 20:39:27 +0200	[thread overview]
Message-ID: <20190507183927.GA58030@gmail.com> (raw)
In-Reply-To: <20190507165743.GX2606@hirez.programming.kicks-ass.net>


* Peter Zijlstra <peterz@infradead.org> wrote:

> On Tue, May 07, 2019 at 09:45:47AM -0700, Alexei Starovoitov wrote:
> > On Wed, Apr 24, 2019 at 5:52 AM Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > On Wed, Apr 24, 2019 at 08:42:40AM -0400, Kairui Song wrote:
> > >
> > > > Sure, the updated comments looks much better. Will the maintainer
> > > > squash the comment update or should I send a V5?
> > >
> > > I've squashed it, I've just not gotten around to stuffing it a git tree
> > > yet. Should happen 'soon'.
> > 
> > Was it applied and on the way to Linus yet ?
> 
> AFAICT it has already landed in Linus' tree.

Yeah, it's now the following commit upstream:

  d15d356887e7: perf/x86: Make perf callchains work without CONFIG_FRAME_POINTER

Thanks,

	Ingo

  reply	other threads:[~2019-05-07 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-22 16:26 [RFC PATCH v4] perf/x86: make perf callchain work without CONFIG_FRAME_POINTER Kairui Song
2019-04-23 11:35 ` Peter Zijlstra
2019-04-24 12:42   ` Kairui Song
2019-04-24 12:52     ` Peter Zijlstra
2019-05-07 16:45       ` Alexei Starovoitov
2019-05-07 16:57         ` Peter Zijlstra
2019-05-07 18:39           ` Ingo Molnar [this message]
2019-04-29  6:37 ` [tip:perf/core] perf/x86: Make perf callchains " tip-bot for Kairui Song

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=20190507183927.GA58030@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bp@alien8.de \
    --cc=dyoung@redhat.com \
    --cc=jolsa@redhat.com \
    --cc=jpoimboe@redhat.com \
    --cc=kasong@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.