From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Robert Richter <rric@kernel.org>,
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 16:28:14 -0300 [thread overview]
Message-ID: <20140630192814.GD4762@kernel.org> (raw)
In-Reply-To: <20140630151802.GG4766@pd.tnic>
Em Mon, Jun 30, 2014 at 05:18:02PM +0200, Borislav Petkov escreveu:
> On Mon, Jun 30, 2014 at 11:58:31AM -0300, Arnaldo Carvalho de Melo wrote:
> > 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.
>
> Sure.
>
> Btw, should I still be working on the split even if the RAS daemon is
> out-of-tree?
>
> If I do, the advantage is that there'll be no pressure on anyone and
> we'll be applying patches as they come.
Yes, I think we should continue moving stuff out of tools/perf/ and into
a place that can be shared with other tools/ living codebases.
Doing so will of course help tools that live elsewhere, outside the
kernel sources as well.
I thought that one way to overcome the fact that the ras daemon doesn't
live in the kernel sources (now or ever) would be to pick whatever lower
hanging fruits there are in place, like:
[acme@zoo linux]$ find tools/ -name list.h
tools/firewire/list.h
tools/lib/lockdep/uinclude/linux/list.h
tools/perf/util/include/linux/list.h
[acme@zoo linux]$
Haven't found much more than that tho at this point.
- Arnaldo
next prev parent reply other threads:[~2014-06-30 19:28 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
2014-06-30 15:18 ` Borislav Petkov
2014-06-30 19:28 ` Arnaldo Carvalho de Melo [this message]
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=20140630192814.GD4762@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).