public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [BUG] perf timechart segfault
Date: Wed, 2 Oct 2013 15:26:31 +0200	[thread overview]
Message-ID: <20131002132631.GC27811@gmail.com> (raw)
In-Reply-To: <CALkWK0ny7MT=5uWykERjKrAe5Odpq72gsFneQB6z1jNHYu6xsw@mail.gmail.com>


* Ramkumar Ramachandra <artagnon@gmail.com> wrote:

> Jiri Olsa wrote:
> > looks like you're missing this one:
> > (git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux perf/core)
> 
> Very messy; doesn't rebase on top of the latest torvalds/linux.git 
> cleanly: I get a merge conflict at patch 9 of 74. Since my work is based 
> on torvalds/linux.git, I was hoping to rebase it on top of Arnaldo's 
> tree, but that results in conflicts too: I'm resolving them now.
> 
> Are the merge windows always this large? Why isn't Arnaldo's tree listed 
> in MAINTAINERS?

note that it's Arnaldo's development tree, not a tree to generally base 
pull requests on - that is what tip:perf/core is for.

Thanks,

	Ingo

  reply	other threads:[~2013-10-02 13:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 11:06 [BUG] perf timechart segfault Ramkumar Ramachandra
2013-10-02 11:19 ` Jiri Olsa
2013-10-02 11:33   ` Ramkumar Ramachandra
2013-10-02 11:59     ` Jiri Olsa
2013-10-02 12:13       ` Ingo Molnar
2013-10-02 15:33         ` Arnaldo Carvalho de Melo
2013-10-02 13:10       ` Ramkumar Ramachandra
2013-10-02 13:26         ` Ingo Molnar [this message]
2013-10-02 16:12       ` Arnaldo Carvalho de Melo

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=20131002132631.GC27811@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@ghostprotocols.net \
    --cc=artagnon@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@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