From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Robert Richter <rric@kernel.org>
Cc: Borislav Petkov <bp@alien8.de>,
Jean Pihet <jean.pihet@linaro.org>, Fu Wei <fu.wei@linaro.org>,
Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@gmail.com>
Subject: Re: crazy idea (was: Re: [PATCH] perf tool: Carve out ctype.h et al)
Date: Mon, 30 Jun 2014 11:58:31 -0300 [thread overview]
Message-ID: <20140630145831.GA4762@kernel.org> (raw)
In-Reply-To: <20140630145031.GR27560@rric.localhost>
Em Mon, Jun 30, 2014 at 04:50:31PM +0200, Robert Richter escreveu:
> On 30.06.14 12:01:15, Borislav Petkov wrote:
> > Well, do you have it as a standalong program? If so, you can put it in
> > a repo somewhere and we can start hacking away and playing with it. If
> > not, we will have to copy the perf code *into* the RAS daemon first so
> > that we can have a separate source on which we all can work on.
> > Someone should be a maintainer of some sorts who merges the patches.
> > And we will continue working on the split so that once the perf tool is
> > properly separated, we can switch to it in the RAS daemon and drop the
> > copied code.
> > This is, to me at least, the best possible thing we can do right now so
> > as not to slow us all down.
> > Any other opinions?
> Perfectly fine with me.
Yeap, guess its the most sensible to do given how things went so far.
Please submit patches when you fix things on code copied from
tools/perf/ and generally when improving it.
- Arnaldo
next prev parent reply other threads:[~2014-06-30 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 7:07 crazy idea (was: Re: [PATCH] perf tool: Carve out ctype.h et al) Borislav Petkov
2014-06-30 9:39 ` Jean Pihet
2014-06-30 10:01 ` Borislav Petkov
2014-06-30 14:50 ` Robert Richter
2014-06-30 14:58 ` Arnaldo Carvalho de Melo [this message]
2014-06-30 15:18 ` Borislav Petkov
2014-06-30 19:28 ` Arnaldo Carvalho de Melo
2014-06-30 19:39 ` Borislav Petkov
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=20140630145831.GA4762@kernel.org \
--to=acme@kernel.org \
--cc=bp@alien8.de \
--cc=dsahern@gmail.com \
--cc=fu.wei@linaro.org \
--cc=jean.pihet@linaro.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=peterz@infradead.org \
--cc=rric@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;
as well as URLs for NNTP newsgroup(s).