linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Jean Pihet <jean.pihet@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Robert Richter <rric@kernel.org>
Subject: Re: [PATCH] tools:perf: move tools/perf/util to tools/lib/perf_util
Date: Thu, 12 Jun 2014 16:01:20 +0200	[thread overview]
Message-ID: <20140612140119.GD4857@pd.tnic> (raw)
In-Reply-To: <CAFrcx1kfUkFF9ROy2C0gcFe88aOHfv2qJBfO+uv+Z7ZW5HxQCw@mail.gmail.com>

On Thu, Jun 12, 2014 at 03:19:50PM +0200, Jean Pihet wrote:
> The idea is to move the re-usable code in libraries, so that other
> tools than perf can use it as well.

Of course it is - didn't I say that too?

> > And I told Jean repeatedly that this needs to be splitted slowly, in
> > smaller libraries like we've been discussing it numerous times.
> Hrrr. I see it as a first move, later the rest of the code can be
> moved the same way.
> Now it seems that moving all from util/ at once is too much. How do
> you see it happening?
> 
> Note: moving some code in the perf source is hairy enough (cf. the
> simplicity of the Makefiles ;-) and so I do not want to re-do it all
> over again too many times.

You're encountering the *exact* *same* issues I was fighting with. And I
was trying to save you that work because I did that conversion a couple
of times already! And hell yeah it is a *lot* of work! And a lot of
*wasted* work at that. Except maybe the fact that it gives you a rough
idea of what needs to be done.

So, for example, looka here:

http://lkml.kernel.org/r/20140612112534.GA24194@gmail.com

Borislav Petkov (4):
      perf tools: Move u64_swap union
      tools: Unify export.h
      tools: Consolidate types.h
      perf/events/core: Drop unused variable after cleanup

4 patches dealing with more or less one thing. No more. Once they're
accepted, you do another so many. And rinse and repeat.

And I've forwarded you the mails of how we want to split them with
Ingo's and acme's thoughts.

In any case, this is the only way I know of currently, which seems to
work right now with the amount of patches going into perf tool and with
the bandwidth of reviewers.

Additionally, if you'd like, we could sync among each other on who does
what. Maybe Robert would like to help too.

HTH.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-06-12 14:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12  8:26 [PATCH] tools:perf: move tools/perf/util to tools/lib/perf_util Jean Pihet
2014-06-12 12:34 ` Arnaldo Carvalho de Melo
2014-06-12 12:49   ` Borislav Petkov
2014-06-12 13:19     ` Jean Pihet
2014-06-12 14:01       ` Borislav Petkov [this message]
2014-06-13 14:03         ` Robert Richter

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=20140612140119.GD4857@pd.tnic \
    --to=bp@alien8.de \
    --cc=acme@kernel.org \
    --cc=jean.pihet@linaro.org \
    --cc=jolsa@redhat.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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).